dbcve.org
Zoorum CommentsWordPress extension · Zoorum

CVE-2025-2163

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-15
Fix available
A fix is available. Upgrade to after 0.9 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Zoorum Comments WordPress plugin has a Cross-Site Request Forgery (CSRF) vulnerability in the zoorum_set_options() function due to missing or incorrect nonce validation. This allows unauthenticated attackers to forge administrative requests by tricking site admins into clicking malicious links, enabling setting modifications and potential script injection.

MitigationUpdate the plugin to a patched version once available. Until then, enforce admin awareness of phishing links and consider disabling the plugin if settings manipulation is a high risk.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Zoorum CommentsWordPress extension
Affected:<= 0.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Zoorum Comments plugin is installed
    Check your WordPress plugins directory or navigate to Plugins > Installed Plugins in the WordPress admin panel and look for 'Zoorum Zoorum Comments' or 'Zoorum Comments'
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed version
    In the WordPress admin panel, click on the plugin to view its details, or inspect the plugin's main PHP file header for the 'Version' comment tag
    Affected if The version number is 0.9 or lower (for example, 0.9, 0.8, 0.7, etc.)
  3. Verify the plugin is active
    Check the Plugins page in WordPress admin - the plugin status should show as 'Active'
    Affected if The plugin is currently activated on the site
  4. Check if settings can be accessed via URL
    Look for any WordPress admin pages under the Zoorum plugin menu (typically at /wp-admin/admin.php?page=zoorum* or similar) - attempt to access settings pages if they exist
    Affected if The plugin exposes any settings or options functionality accessible to administrators
  5. Confirm admin user exposure to phishing
    Review whether administrators are trained to recognize and avoid clicking on untrusted links, as the vulnerability requires tricking an admin into clicking a malicious URL
    Affected if Admins may potentially click on crafted links sent via email, comments, or other channels

Your environment is affected if the Zoorum Comments plugin version 0.9 or lower is installed and active, and administrators could be tricked into clicking malicious links that exploit the missing nonce validation in the zoorum_set_options() function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.9
Interim mitigation

Update the plugin to a patched version once available. Until then, enforce admin awareness of phishing links and consider disabling the plugin if settings manipulation is a high risk.

Recommended fix Moderate confidence

Contact plugin developer or check WordPress plugin repository for post-0.9 fixed release

  1. 1. Check the WordPress plugin repository or contact the plugin developer to confirm if a patched version of Zoorum Comments has been released
  2. 2. If a patched version is available, navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Locate Zoorum Comments plugin and update to the latest patched version
  4. 4. After updating, verify the plugin settings have not been tampered with by reviewing the plugin configuration
  5. 5. If no patched version is available, consider disabling the plugin until a fix is released, or implement additional CSRF protections at the server level

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zoorum Comments Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2163 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2163 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data