Social Share BoostWordPress extension · Sumo
CVE-2023-25033
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 Sumo Social Share Boost plugin <= 4.5 versions.
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 Sumo Social Share Boost WordPress plugin affecting versions 4.5 and below. The vulnerability allows attackers to trick authenticated administrators into performing unintended actions (such as modifying plugin settings) by exploiting the lack of anti-CSRF tokens in the plugin's administrative forms and AJAX actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Social Share BoostWordPress extension
<= 4.5CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Confirm plugin is installedLog in to WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Sumo Social Share Boost' in the list of active or inactive plugins.Affected if Plugin is present in the WordPress installation, regardless of activation status
-
Check installed versionIn the Plugins list, find Sumo Social Share Boost and note the version number displayed beneath the plugin name. Alternatively, open the main plugin file (sumo-social-share-boost.php) and locate the 'Version' header comment.Affected if Version is 4.5 or lower
-
Inspect admin forms for nonce fieldsNavigate to the plugin settings pages in WordPress admin. View the page source (right-click > View Page Source) and search for 'wp_nonce' or '_wpnonce' within the plugin's form tags. Check if each form that modifies settings contains a nonce field.Affected if Forms on plugin settings pages lack wp_nonce_field or _wpnonce parameters
-
Check AJAX handlers for nonce verificationLocate the plugin's AJAX action handlers in the codebase (search for 'add_action' with 'wp_ajax'). Examine each handler to verify it calls 'check_ajax_referer' or 'wp_verify_nonce' before processing state-changing requests.Affected if AJAX endpoints that modify data do not verify nonces before executing
User is affected if Sumo Social Share Boost is installed at version 4.5 or below and the plugin's administrative forms or AJAX actions lack proper nonce validation.
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 Sumo Social Share Boost plugin to a version newer than 4.5, or implement anti-CSRF tokens (nonces) on all state-changing form submissions and AJAX endpoints within the plugin.
Fix this in Social Share Boost
Scoped from the published advisory
- 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-2023-25033 — 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-2023-25033 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