CVE-2025-2163: The Zoorum Comments plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, an

Q: How do I fix CVE-2025-2163?

zoorum comments: upgrade to newer than 0.9. Exact commands for each OS are on this page.

Q: Is CVE-2025-2163 being exploited?

CVE-2025-2163 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-2163 affect?

CVE-2025-2163 affects zoorum comments. Severity is medium (CVSS 6.1). 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 possib

Q: How urgent is CVE-2025-2163?

Priority 23/100. No elevated risk signals yet.

Routine

MEDIUM 6.1UPGRADE

CVE-2025-2163 is a medium-severity flaw (CVSS 6.1) affecting zoorum comments. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 92%)
CISA exploited list	No
Weakness	CWE-79, CWE-352
Published	2025-03-15
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: zoorum

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-03-15 04:15 UTCPublished CVE record published
2026-06-17 09:06 UTCUpdated Record last modified

zoorum zoorum comments UPGRADE

Affected: <= 0.9

Fixed in: newer than 0.9

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy zoorum-comments || rpm -q zoorum-comments || zoorum-comments --version

2. UPGRADE to newer than 0.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade zoorum-comments

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade zoorum-comments

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-2163?

zoorum comments: upgrade to newer than 0.9. Exact commands for each OS are on this page.

Is CVE-2025-2163 being exploited?

CVE-2025-2163 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-2163 affect?

CVE-2025-2163 affects zoorum comments. Severity is medium (CVSS 6.1). 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 possib

How urgent is CVE-2025-2163?

Priority 23/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs