CVE-2026-2432
Stored XSS in CM Custom Reports Plugin Affects WordPress Multisites
Publication date: 2026-03-20
Last updated on: 2026-03-20
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| cm_custom_reports | cm_custom_reports | to 1.2.7 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The CM Custom Reports β Flexible reporting to track what matters most plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) via admin settings in all versions up to and including 1.2.7.
This vulnerability occurs due to insufficient input sanitization and output escaping, allowing authenticated attackers with administrator-level permissions or higher to inject arbitrary web scripts into pages.
These injected scripts execute whenever a user accesses the affected page. The vulnerability specifically affects multi-site installations and installations where the WordPress setting 'unfiltered_html' has been disabled.
How can this vulnerability impact me? :
This vulnerability allows an attacker with administrator-level access to inject malicious scripts that execute in the context of other users viewing the injected pages.
Potential impacts include theft of user credentials, session hijacking, unauthorized actions performed on behalf of users, and the spread of malware or phishing attacks within the affected WordPress multi-site environment.
Because the vulnerability requires high privileges to exploit, it primarily risks environments where trusted users or administrators might be compromised or act maliciously.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability affects all versions of the CM Custom Reports β Flexible reporting to track what matters most plugin for WordPress up to and including version 1.2.7.
To mitigate this vulnerability, you should update the plugin to a version later than 1.2.7 where the issue is fixed.
Additionally, since the vulnerability only affects multi-site installations and installations where unfiltered_html has been disabled, reviewing your WordPress configuration for these conditions may help reduce risk.
Ensure that only trusted administrators have access to the plugin settings, as the vulnerability requires administrator-level permissions to exploit.