Concrete CMS before 9.5.3 improperly neutralized a user-supplied custom date format when rendering conversation messages, resulting in reflected… (CVE-2026-81925)
Concrete CMS versions prior to 9.5.3 contain a reflected cross-site scripting (XSS) vulnerability due to improper neutralization of user-supplied custom date formats in conversation message rendering. This flaw allows attackers to execute arbitrary JavaScript in the browsers of users who submit crafted POST requests to the conversation view endpoint. The vulnerability is exacerbated by the lack of a CSRF token on this endpoint, enabling cross-origin POST requests without authentication. The Concrete CMS security team assigned this issue a low severity rating with a CVSS v4.0 score of 2.1.
AI Analysis
Technical Summary
Concrete CMS before version 9.5.3 improperly neutralizes user-supplied custom date formats when rendering conversation messages, leading to a reflected cross-site scripting vulnerability (CWE-79). An attacker can exploit this by tricking a user into submitting a crafted POST request to the conversation view endpoint, which lacks CSRF protection, allowing execution of arbitrary JavaScript in the victim's browser. The vulnerability has a CVSS v4.0 base score of 2.1, indicating low severity. No known exploits in the wild have been reported. No patch links or vendor advisory details are provided in the input data.
Potential Impact
Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of the victim's browser session when interacting with the conversation view endpoint. This could lead to session hijacking or other client-side attacks. However, the low CVSS score and requirement for user interaction reduce the overall risk.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should exercise caution when interacting with conversation messages and avoid submitting untrusted POST requests. The absence of a CSRF token on the endpoint suggests that adding CSRF protection would mitigate the issue.
Concrete CMS before 9.5.3 improperly neutralized a user-supplied custom date format when rendering conversation messages, resulting in reflected… (CVE-2026-81925)
Description
Concrete CMS versions prior to 9.5.3 contain a reflected cross-site scripting (XSS) vulnerability due to improper neutralization of user-supplied custom date formats in conversation message rendering. This flaw allows attackers to execute arbitrary JavaScript in the browsers of users who submit crafted POST requests to the conversation view endpoint. The vulnerability is exacerbated by the lack of a CSRF token on this endpoint, enabling cross-origin POST requests without authentication. The Concrete CMS security team assigned this issue a low severity rating with a CVSS v4.0 score of 2.1.
CVSS v4.0
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Concrete CMS before version 9.5.3 improperly neutralizes user-supplied custom date formats when rendering conversation messages, leading to a reflected cross-site scripting vulnerability (CWE-79). An attacker can exploit this by tricking a user into submitting a crafted POST request to the conversation view endpoint, which lacks CSRF protection, allowing execution of arbitrary JavaScript in the victim's browser. The vulnerability has a CVSS v4.0 base score of 2.1, indicating low severity. No known exploits in the wild have been reported. No patch links or vendor advisory details are provided in the input data.
Potential Impact
Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of the victim's browser session when interacting with the conversation view endpoint. This could lead to session hijacking or other client-side attacks. However, the low CVSS score and requirement for user interaction reduce the overall risk.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should exercise caution when interacting with conversation messages and avoid submitting untrusted POST requests. The absence of a CSRF token on the endpoint suggests that adding CSRF protection would mitigate the issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3mw6-rrq3-376v
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-81925"]
- Database Specific Severity
- LOW
- Cvss Version
- 4.0
Threat ID: 6aaa07e455bf5e2cf5ea33fc
Added to database: 09/16/2026, 03:07:16 UTC
Last enriched: 09/16/2026, 04:47:13 UTC
Last updated: 09/16/2026, 22:01:39 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.