CVE-2025-2163 json
Zoorum Comments <= 0.9 - Cross-Site Request Forgery to Stored Cross-Site Scripting
published last yr. modified 4mo ago also EUVD-2025-6618
- cvss
- 6.1
- 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 7%
- public exploits
- 0
- none known
Summary
The Zoorum Comments plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.9. This is due to missing or incorrect nonce validation on the zoorum_set_options() function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Is CVE-2025-2163 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N |
Affected products
- zoorum Zoorum Comments
Classification
- Weakness
- Technology feeds
References
-
wordfence.com
/threat-intel/vulnerabilities/id/2b58fb0f-c7ac-4ee6-84f1-ac14617a7c2b?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/zoorum-comments/tags/0.9/zoorum-comments-admin.php#L18
broken-link
-
plugins.trac.wordpress.org
/browser/zoorum-comments/tags/0.9/zoorum-comments-admin.php#L38
broken-link
-
wordpress.org
/plugins/zoorum-comments/
product
Sources
- CVE List CVE-2025-2163
- NVD CVE-2025-2163
Fencer Intel 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.