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

CVE-2025-23691

HIGH · 7.1 CVSS v3.1 Published 2025-01-16
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 Braulio Aquino Send to Twitter send-to-twitter allows Stored XSS.This issue affects Send to Twitter: from n/a through <= 1.7.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 · moderate confidence

CSRF vulnerability in the Send to Twitter WordPress plugin allows attackers to craft malicious requests that trick authenticated administrators into inadvertently executing actions. Combined with stored XSS, this enables injection of persistent malicious scripts that execute when other users interact with affected Twitter-sent content.

MitigationUpdate to a patched version of the plugin once released; in the meantime, restrict administrative access to trusted users only and consider disabling the plugin until patched.

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 Send to Twitter plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Send to Twitter' or 'send-to-twitter' in the plugin list
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    Click on the plugin name in the Plugins list to view version details, or inspect the plugin main file header in wp-content/plugins/send-to-twitter/
    Affected if Version cannot be determined or is earlier than the patched release
  3. Confirm plugin is active
    In Plugins > Installed Plugins, verify the 'Send to Twitter' plugin has 'Active' status under the plugin name
    Affected if Plugin is active and running
  4. Check for configured Twitter credentials
    Go to plugin settings (usually under Settings > Send to Twitter or similar) and check if Twitter API credentials are saved and the connection is active
    Affected if Twitter posting feature is enabled with valid credentials configured
  5. Inspect recent posts for suspicious content
    Review recent posts/pages for unexpected JavaScript payloads or links that may have been injected via the stored XSS, check post content fields for script tags or event handlers
    Affected if Unexpected scripts or anomalous content found in posts that were published while the plugin was active

If the Send to Twitter plugin is installed and active, the environment may be affected by this CSRF and stored XSS vulnerability; compare your version to any patched release once available.

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

Update to a patched version of the plugin once released; in the meantime, restrict administrative access to trusted users only and consider disabling the plugin until patched.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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