CVE-2025-25074
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 Nirmal Kumar Ram WP Social Stream wp-social-stream allows Stored XSS.This issue affects WP Social Stream: from n/a through <= 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 confidenceA CSRF vulnerability in the WP Social Stream WordPress plugin (versions through 1.1) allows attackers to craft malicious requests that, when triggered by an authenticated administrator, cause stored XSS to be persisted. The lack of anti-CSRF tokens (nonces) on sensitive actions enables attackers to inject malicious scripts that execute when other users view the affected content.
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 WP Social Stream plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Social Stream' in the list. Note whether it is active or inactive.Affected if The plugin is installed and active (inactive plugins still present the vulnerability code but it cannot be triggered)
-
Check the installed plugin versionClick 'View details' on the WP Social Stream plugin in the Plugins page, or inspect the plugin main file header for the 'Version' field. Compare the version number to the affected range (1.1 and below).Affected if The installed version is 1.1 or any version below 1.1
-
Inspect plugin admin forms for nonce fieldsNavigate to the plugin admin pages (typically under WP Social Stream menu). View page source or inspect form HTML elements. Look for input fields containing 'nonce' (such as wp_nonce_field), typically named '_wpnonce' or '_wp_nonce'.Affected if Admin forms and action URLs do not contain nonce fields or parameters
-
Check plugin PHP code for nonce verificationAccess the plugin directory via file manager or FTP (wp-content/plugins/wp-social-stream). Open main PHP files and search for 'wp_verify_nonce', 'check_admin_referer', or 'wp_nonce_field' function calls around form processing and admin action handlers.Affected if Sensitive admin actions (settings saves, content updates, etc.) lack nonce verification code
You are affected if WP Social Stream plugin versions 1.1 or below are installed and the plugin lacks nonce implementation on its admin forms and actions.
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 dataImplement WordPress nonces (wp_nonce_field) on all forms and administrative actions, and verify nonces (wp_verify_nonce) on submission to prevent CSRF attacks and the resulting stored XSS.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25074 — 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-25074 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