CVE-2025-14035 json
DebateMaster <= 1.0.0 - Authenticated (Administrator+) Stored Cross-Site Scripting via Color Options via 'debate' Shortcode
published 2025-12-12 10 mo ago modified 2026-10-07 32 d ago also EUVD-2025-202980
- cvss
- 4.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
The DebateMaster plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the color options in the plugin settings in all versions up to, and including, 1.0.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses a page with the debate shortcode. This only affects multi-site installations and installations where unfiltered_html has been disabled.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 10 mo ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.4 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N |
Affected products
- jeremybmerrill DebateMaster
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/a68cb059-972f-473d-90cb-41ccda052b08?source=cve
- wordpress.org /plugins/debatemaster/
- plugins.trac.wordpress.org /browser/debatemaster/trunk/debatemaster.php#L30
- plugins.trac.wordpress.org /browser/debatemaster/tags/1.0.0/debatemaster.php#L30
- plugins.trac.wordpress.org /browser/debatemaster/trunk/debatemaster.php#L87
- plugins.trac.wordpress.org /browser/debatemaster/tags/1.0.0/debatemaster.php#L87
Sources
- CVE List CVE-2025-14035
- NVD CVE-2025-14035
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.