dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-22705

HIGH · 7.1 CVSS v3.1 Published 2025-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in godthor Disqus Popular Posts disqus-popular-posts allows Reflected XSS.This issue affects Disqus Popular Posts: from n/a through <= 2.1.1.

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

A Cross-Site Request Forgery (CSRF) vulnerability in the Disqus Popular Posts plugin (versions up to 2.1.1) allows attackers to craft malicious requests that result in Reflected XSS. This occurs because the plugin does not properly validate the origin of requests or sanitize output, enabling attackers to execute arbitrary JavaScript in victim browsers via crafted links or forms.

MitigationImplement anti-CSRF tokens (nonces) for state-changing operations and apply proper output encoding/sanitization to prevent reflected XSS. Until an official patch is released, disable or remove the plugin.

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

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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Locate the Disqus Popular Posts plugin
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Disqus Popular Posts' or 'disqus-popular-posts'. Alternatively, check the wp-content/plugins directory for a folder named 'disqus-popular-posts' or similar.
    Affected if The plugin folder exists in the WordPress installation.
  2. Identify the installed version
    In the WordPress plugin list, locate the Disqus Popular Posts entry and read the version number displayed under the plugin name. If using file inspection, open the main plugin PHP file (usually disqus-popular-posts.php or similar) and look for a 'Version' header in the plugin comments.
    Affected if The installed version is 2.1.1 or any earlier version (up to and including 2.1.1).
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify that the Disqus Popular Posts plugin shows as 'Active' rather than 'Inactive' or 'Not installed'.
    Affected if The plugin is currently activated on the WordPress site.
  4. Check for CSRF token implementation
    Inspect the plugin's PHP source code for state-changing actions (form submissions, AJAX calls, settings updates). Look for the presence of WordPress nonces using functions like wp_create_nonce, wp_nonce_field, or check_admin_referer. If these are missing from forms or AJAX handlers, the vulnerability is present.
    Affected if No anti-CSRF nonces are found in the plugin's form handlers or AJAX endpoints.
  5. Inspect for reflected XSS sanitization gaps
    Review the plugin code for output handling functions. Check if user-supplied parameters (GET/POST) are echoed back without sanitization. Look for use of functions like echo, print, or printf on raw $_GET, $_POST, or $_REQUEST values without esc_html, esc_attr, or similar escaping functions.
    Affected if User input from request parameters is output without proper escaping.

A user is affected if the Disqus Popular Posts plugin (versions up to 2.1.1) is installed and active, with no CSRF tokens protecting forms and unsanitized output reflecting user input.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonces) for state-changing operations and apply proper output encoding/sanitization to prevent reflected XSS. Until an official patch is released, disable or remove the plugin.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22705 — 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-22705 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