CVE-2025-26580
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Complete SEO Page/Post Specific Social Share Buttons pagepost-specific-social-share-buttons allows Stored XSS.This issue affects Page/Post Specific Social Share Buttons: from n/a through <= 2.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Page/Post Specific Social Share Buttons WordPress plugin (versions <= 2.1) allows attackers to inject malicious scripts through Stored XSS by tricking authenticated administrators into triggering crafted requests.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Page/Post Specific Social Share Buttons' in the list. Note whether it is active or inactive.Affected if The plugin is installed and active, and its version is 2.1 or lower
-
Check the installed plugin versionIn the Plugins list, find the plugin and view the version number displayed below the plugin name. Compare this version to the affected range: version 2.1 or lower.Affected if The displayed version number is 2.1 or lower (for example, 2.1, 2.0.9, 1.5, etc.)
-
Inspect plugin settings for suspicious contentNavigate to the plugin settings page (usually under Settings or the plugin's own menu item) and examine all text fields, especially buttons, labels, or social media configuration fields for any unexpected script tags, HTML elements, or encoded payloads.Affected if Any plugin setting fields contain script tags, onclick handlers, or other JavaScript code that was not intentionally added by an administrator
-
Review the plugin source code for CSRF protectionAccess the plugin files via FTP or file manager in wp-content/plugins/page-post-specific-social-share/. Open the main plugin PHP file and search for 'nonce', 'wp_verify_nonce', 'check_admin_referer', or similar WordPress nonce verification functions.Affected if The plugin code lacks nonce verification or request origin validation on settings save actions, or the verification is present but incorrectly implemented
A user is affected if the Page/Post Specific Social Share Buttons plugin is installed at version 2.1 or lower and either contains malicious XSS payloads in its settings or lacks proper CSRF protection in its code.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to the latest version; implement anti-CSRF tokens and proper request origin validation; audit existing content for injected XSS payloads.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26580 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26580 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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