MediumPublic exploit

Reflected XSS in Concrete CMS Conversation Messages Dashboard Page

IdentifiersCVE-2025-8571CWE-79· Improper Neutralization of Input…

CVE-2025-8571 is a reflected cross-site scripting vulnerability in Concrete CMS affecting version 9 through 9.4.2 and versions prior to 8.5.21. The issue is present in the Conversation Messages Dashboard Page, where user-controlled input is not properly sanitized before being reflected back to the browser. An attacker can craft a malicious request or link containing script payloads that execute in the context of a victim’s authenticated Concrete CMS session when the victim accesses the vulnerable page.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can lead to theft of session cookies or anti-CSRF tokens, defacement or manipulation of web content presented to the victim, and redirection to attacker-controlled or malicious sites. If the victim has administrative privileges, the XSS can be used to perform unauthorized actions within Concrete CMS with the victim’s privileges.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to the Concrete CMS dashboard to trusted administrators only, reduce exposure of the affected administrative interface, and monitor for suspicious links or requests targeting the Conversation Messages Dashboard Page. Standard XSS hardening measures such as rigorous output encoding, input validation, and use of browser-side protections including a restrictive Content Security Policy may reduce risk, but vendor-provided fixed versions should be treated as the primary remediation.

Remediation

Patch, then assume compromise.

Upgrade Concrete CMS to 8.5.21 or later on the 8.5.x branch, or to 9.4.3 or later on the 9.x branch.

PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app

CVE-2025-8571MaturityOperationalVerified exploit

This repository contains a Python exploit script (CVE-2025-8570.py) targeting a vulnerability in the 'grind-mobile-app' plugin for WordPress. The exploit abuses insecure JWT handling to impersonate users and update their account information via the /wp-json/grind-mobile-app/v1/customers/1 REST API endpoint. The script generates or accepts a JWT token, crafts a PUT request with attacker-supplied user data (email, first name, last name, username, password), and sends it to the vulnerable endpoint. The exploit is operational and allows for account takeover or privilege escalation if the target is vulnerable. The repository also contains a minimal README.md, which appears to reference a different CVE (CVE-2025-8571), likely a typo. The main entry point is CVE-2025-8570.py, written in Python, and no framework is used.

chimdi2700Disclosed Sep 12, 2025pythonnetwork

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

Concrete CMSConcrete Cmsapplication

Concrete5Concrete5application

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

3 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3