CVE-2025-10178 json
CM Business Directory <= 1.5.2 - Authenticated (Contributor+) Stored Cross-Site Scripting
published 2025-09-26 13 mo ago modified 2026-10-11 28 d ago also EUVD-2025-31203
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
The CM Business Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'cmbd_featured_image' shortcode in all versions up to, and including, 1.5.2 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 13 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- creativemindssolutions CM Business Directory – Optimise and showcase local business
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/2c1ecd71-57ed-44ba-a007-3b96b98d3bf7?source=cve
- plugins.trac.wordpress.org /browser/cm-business-directory/trunk/frontend/cm-business-directory-business-page-sc.php#L289
- wordpress.org /plugins/cm-business-directory/
- plugins.trac.wordpress.org /browser/cm-business-directory/trunk/frontend/cm-business-directory-business-page-sc.php?rev=3364840#L280
- plugins.trac.wordpress.org /browser/cm-business-directory/tags/1.5.2/frontend/cm-business-directory-business-page-sc.php#L289
Sources
- CVE List CVE-2025-10178
- NVD CVE-2025-10178
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.