CVE-2025-31393
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 vfvalent Social Bookmarking RELOADED social-bookmarking-reloaded allows Stored XSS.This issue affects Social Bookmarking RELOADED: from n/a through <= 3.18.
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 confidenceCSRF vulnerability in the Social Bookmarking RELOADED WordPress plugin enables attackers to trick authenticated administrators into unknowingly submitting malicious requests that inject persistent XSS payloads into stored bookmarks, which then execute when other users view those bookmarks.
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 Social Bookmarking RELOADED plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'Social Bookmarking RELOADED' or check the plugins directory for this plugin folderAffected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn the Plugins list, locate the Social Bookmarking RELOADED entry and read the version number displayed beneath the plugin name; alternatively, inspect the main plugin file header for the 'Version' tagAffected if The version cannot be determined or is earlier than the patched release containing the fix
-
Check if the bookmark creation/editing feature is in useNavigate to the plugin settings page (usually under Settings or the plugin's own menu) and review if bookmark configuration forms are accessible or have been usedAffected if The plugin settings page exists and bookmark forms are present and functional
-
Inspect stored bookmarks for suspicious contentAccess the database table storing bookmarks (typically wp_options or a custom table depending on plugin structure) and query for bookmark entries containing script tags, event handlers, or encoded characters typical of XSS payloadsAffected if Any bookmark entries contain unencoded HTML tags, JavaScript code, or unusual script-like patterns
-
Review admin action logs for unauthorized requestsCheck server access logs and any available WordPress audit logs for POST requests to the plugin's bookmark submission endpoint originating from the admin account but containing unexpected or encoded parametersAffected if There are logged admin actions with malformed or suspicious parameter values in bookmark-related requests
If the Social Bookmarking RELOADED plugin is installed without the CVE fix, the bookmark feature is active, and stored bookmarks contain malicious scripts, the environment is affected by this vulnerability.
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 dataAdd anti-CSRF tokens to all state-changing form actions and implement proper input sanitization with context-aware output encoding to prevent XSS injection.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31393 — 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-31393 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