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

CVE-2025-49381

CRITICAL · 9.6 CVSS v3.1 Published 2025-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 ads.txt Guru ads.txt Guru Connect adstxt-guru-connect allows Cross Site Request Forgery.This issue affects ads.txt Guru Connect: from n/a through <= 1.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

Cross-Site Request Forgery (CSRF) vulnerability in the ads.txt Guru Connect WordPress plugin allows attackers to induce authenticated administrators to perform unintended state-changing actions (such as modifying ads.txt configurations) by tricking them into visiting malicious pages. The plugin fails to implement proper anti-CSRF tokens on sensitive operations.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations (forms, AJAX endpoints) and validate these tokens server-side before processing requests. Additionally, configure SameSite attributes on session cookies.

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
High
Integrity
High
Availability
High

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

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 ads.txt Guru Connect plugin is installed
    Navigate to WordPress admin > Plugins and verify 'ads.txt Guru Connect' is installed and activated
    Affected if The plugin is present and active in the WordPress installation
  2. Identify the installed plugin version
    In Plugins page, click on the plugin details to view the version number, or check the plugin main PHP file header in /wp-content/plugins/ads-txt-guru-connect/
    Affected if The installed version lacks proper anti-CSRF nonce implementation (typically present in unpatched versions)
  3. Inspect admin forms for nonce fields
    View the page source of the plugin admin settings page; search for forms that modify ads.txt and verify they contain hidden nonce fields (wp_nonce_field)
    Affected if Forms that modify ads.txt configuration lack hidden nonce token fields
  4. Check server-side nonce validation
    Examine the plugin PHP code that handles form submissions or AJAX requests; verify the code calls wp_verify_nonce or check_admin_referer before processing state-changing operations
    Affected if The plugin processes admin requests without validating CSRF tokens server-side

If the ads.txt Guru Connect plugin is active and its admin forms or AJAX handlers process requests without validating CSRF tokens (nonces), the installation is vulnerable to CVE-2025-49381.

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) on all state-changing operations (forms, AJAX endpoints) and validate these tokens server-side before processing requests. Additionally, configure SameSite attributes on session cookies.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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