Is CM Custom Reports safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (1.2.10). As of 2026-11-04. 2 issues are on record for older versions; version 3.1.1 or newer fixes all of them that state a fix. Keep CM Custom Reports on the latest version (1.2.10) and remove it if you do not use it.

Which versions of CM Custom Reports are vulnerable?

Known issues on record (newest first): Stored cross-site scripting (XSS) (1.2.7 and older, fixed in 3.1.1); Reflected cross-site scripting (XSS) (1.2.7 and older, fixed in 3.1.1). The full list with sources is on this page.

What is the latest version of CM Custom Reports?

1.2.10, according to wordpress.org (last updated 2026-10-13). It has 100+ active installs.

What should I do if my CM Custom Reports is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update cm-custom-reports). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · cm-custom-reports · data as of 2026-11-04

Is CM Custom Reports safe? Known vulnerabilities and latest version

Latest version: 1.2.10
Last updated: 2026-10-13
Active installs: 100+
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 7.0.8 · PHP 5.2.4+

Generate custom reports and get efficient analytics for your site with the custom reports plugin. Filter data and create tailored reports. — by CreativeMindsSolutions

What to do

Update to the latest version (1.2.10). Anything older than 3.1.1 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get cm-custom-reports --field=version shows what you run; wp plugin update cm-custom-reports updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 4.4 CVE-2026-2432 · published 2026-03-20

Stored cross-site scripting (XSS) in CM Custom Reports (1.2.7 and older)

Affected: 1.2.7 and older
Fixed in: 3.1.1 *
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The CM Custom Reports – Flexible reporting to track what matters most plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.2.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

NVD CVE-2026-2432 Wordfence advisory Code change (fix)Plugin source

medium 6.1 CVE-2026-2431 · published 2026-03-07

Reflected cross-site scripting (XSS) in CM Custom Reports (1.2.7 and older)

Affected: 1.2.7 and older
Fixed in: 3.1.1 *
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The CM Custom Reports plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'date_from' and 'date_to' parameters in all versions up to, and including, 1.2.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

NVD CVE-2026-2431 Wordfence advisory Plugin source

Recent activity

2026-10-13 — latest release on wordpress.org (1.2.10).
2026-03-20 — Stored cross-site scripting (XSS) disclosed (CVE-2026-2432), fixed in 3.1.1.
2026-03-07 — Reflected cross-site scripting (XSS) disclosed (CVE-2026-2431), fixed in 3.1.1.

Free. We check the CVE feeds every day and email you only when a new issue for CM Custom Reports (cm-custom-reports) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (2)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/cm-custom-reports (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/cm-custom-reports"><img src="https://laskyr.com/plugins/cm-custom-reports/badge.svg" alt="CM Custom Reports vulnerability status"></a>

← Check another plugin · Free hacked-site scan