Buddypress Activity Social ShareWordPress extension · Wbcomdesigns
CVE-2023-28694
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 Wbcom Designs Wbcom Designs – BuddyPress Activity Social Share plugin <= 3.5.0 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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the Wbcom Designs BuddyPress Activity Social Share plugin versions 3.5.0 and earlier allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious requests.
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
Buddypress Activity Social ShareWordPress extension
<= 3.5.0CVSS 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.
-
Verify plugin is installedNavigate to WordPress Admin > Plugins > Installed Plugins and look for 'BuddyPress Activity Social Share' by Wbcom Designs. Confirm the plugin appears in the list.Affected if The plugin is present in the WordPress installation
-
Check installed plugin versionIn the Plugins list, locate the 'BuddyPress Activity Social Share' entry and read the version number displayed beneath the plugin name. Alternatively, access the main plugin file (usually in wp-content/plugins/buddypress-activity-social-share/) and inspect the version header in the plugin PHP file.Affected if The version listed is 3.5.0 or lower
-
Confirm plugin is activeIn WordPress Admin > Plugins, verify that the BuddyPress Activity Social Share plugin shows as 'Active' (not deactivated or deleted).Affected if The plugin is currently active and running at a vulnerable version
-
Check WordPress users have permissionsVerify that WordPress users with permission to use BuddyPress activity features exist and can perform social sharing actions (sharing posts to social media). The CSRF affects authenticated users performing these actions.Affected if Authenticated users can access BuddyPress activity sharing features on a site running the vulnerable plugin version
If the BuddyPress Activity Social Share plugin is installed, active, and running at version 3.5.0 or lower, the environment is affected by this CSRF 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 dataUpdate the plugin to version 3.5.1 or later which contains the CSRF fix. As a defensive measure, ensure all state-changing actions implement anti-CSRF tokens and validate the Origin/Referer headers.
Fix this in Buddypress Activity Social Share
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28694 — 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-28694 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