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

CVE-2025-25071

HIGH · 7.1 CVSS v3.1 Published 2025-02-07
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 topplugins Vignette Ads vignete-ads allows Stored XSS.This issue affects Vignette Ads: from n/a through <= 0.2.

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 · high confidence

CSRF vulnerability in the Vignette Ads WordPress plugin (vignete-ads) allows attackers to trick authenticated administrators into submitting malicious requests that inject Stored XSS payloads. The lack of CSRF tokens on admin actions enables the attack without the victim's knowledge.

MitigationAdd anti-CSRF tokens (nonces) to all state-changing admin actions and implement proper input sanitization/output encoding to prevent Stored XSS. Consider disabling or replacing the plugin until fixed, given it appears unmaintained.

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. Verify Vignette Ads plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'vignette ads' or 'vignete-ads'. Note whether the plugin is active.
    Affected if The plugin named 'vignette ads' or 'vignete-ads' is present and active in the WordPress installation.
  2. Identify installed plugin version
    Click 'View details' on the plugin in the WordPress plugins list to reveal the version number, or inspect the plugin main file header for the 'Version' field.
    Affected if The installed version matches any officially listed vulnerable version range (compare your installed version to any officially published vulnerable range for this CVE).
  3. Examine admin forms for CSRF protection
    Navigate to the plugin admin settings page. View the page source or intercept the HTML of any form that changes plugin settings or submits data. Look for a hidden input field named 'nonce' or similar, or check if the form submits to an endpoint that verifies a token.
    Affected if State-changing admin forms (settings save, content submission) lack CSRF token (nonce) verification.
  4. Test for Stored XSS injectability
    From the plugin admin panel, submit a test payload containing HTML/script tags (e.g., <img src=x onerror=alert(1)>) into any text fields the plugin provides. Save the settings and then view the saved output to see if the payload executes or renders unescaped.
    Affected if User-supplied input in plugin settings is stored and rendered without proper sanitization or output encoding, allowing Stored XSS.
  5. Review plugin code for nonce verification
    If file access is available, locate the plugin PHP files (typically in wp-content/plugins/vignete-ads/). Search for 'wp_nonce_field', 'wp_verify_nonce', or 'check_admin_referer' function calls around form handling code.
    Affected if Plugin code handling admin POST/GET requests does not contain CSRF verification functions.

A user is affected if the Vignette Ads plugin is installed, any admin forms lack CSRF token verification, and the plugin stores user input without proper sanitization enabling Stored XSS.

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

Add anti-CSRF tokens (nonces) to all state-changing admin actions and implement proper input sanitization/output encoding to prevent Stored XSS. Consider disabling or replacing the plugin until fixed, given it appears unmaintained.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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