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

CVE-2025-46516

HIGH · 7.1 CVSS v3.1 Published 2025-04-24
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 silencecm Twitter Card Generator twitter-card-generator allows Stored XSS.This issue affects Twitter Card Generator: from n/a through <= 1.0.5.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Twitter Card Generator WordPress plugin allows remote attackers to inject malicious JavaScript through stored XSS by tricking authenticated administrators into visiting a crafted page. The lack of anti-CSRF tokens on state-changing actions enables attackers to silently inject payloads that persist and execute when other users view generated Twitter cards.

MitigationImplement anti-CSRF tokens (nonces) on all form actions and state-changing operations, combined with proper input validation and output sanitization to prevent stored XSS. Upgrade to the latest patched version once available.

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 Twitter Card Generator plugin is installed
    Check WordPress admin under Plugins > Installed Plugins, or inspect the wp-content/plugins directory for a folder named twitter-card-generator or similar.
    Affected if The Twitter Card Generator plugin is present and active on the site.
  2. Identify the installed plugin version
    Open the plugin's main PHP file or readme.txt in the plugin directory and locate the version comment or header.
    Affected if Any version of the Twitter Card Generator plugin is installed; CVE-2025-46516 affects this plugin without a specific patched version provided.
  3. Confirm lack of CSRF protection in plugin code
    Search plugin PHP files for nonce-related functions: wp_verify_nonce, wp_nonce_field, wp_nonce_url, check_admin_referer. Look for these on state-changing form actions like saving settings, generating cards, or updating configurations.
    Affected if The plugin lacks nonce verification or anti-CSRF tokens on forms that modify plugin state.
  4. Verify XSS vulnerability in stored card data
    As an administrator, access the plugin admin panel and examine how card data (titles, descriptions, images, URLs) is processed. Check if user-supplied input is stored and later output without proper sanitization (esc_html, esc_attr, sanitize_text_field).
    Affected if The plugin stores user input without sanitization and outputs it without escaping when rendering Twitter cards.
  5. Test for stored XSS persistence and execution
    Submit a crafted payload containing JavaScript (e.g., <script>alert(1)</script> or <img src=x onerror=alert(1)>) through the card generation form. Then view the generated card as a different user or in a public context.
    Affected if The injected payload persists in stored data and executes when other users view the generated Twitter card.

A site is affected if the Twitter Card Generator WordPress plugin is installed, lacks anti-CSRF nonce protection on state-changing actions, and allows unsanitized input to be stored and rendered as 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

Implement anti-CSRF tokens (nonces) on all form actions and state-changing operations, combined with proper input validation and output sanitization to prevent stored XSS. Upgrade to the latest patched version once available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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