Buddypress Activity PlusWordPress extension · Incsub
CVE-2015-9455
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 · uneditedThe buddypress-activity-plus plugin before 1.6.2 for WordPress has CSRF with resultant directory traversal via the wp-admin/admin-ajax.php bpfb_photos[] parameter in a bpfb_remove_temp_images action.
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 confidenceThe buddypress-activity-plus plugin before version 1.6.2 contains a CSRF vulnerability in the bpfb_remove_temp_images AJAX action that allows directory traversal via the bpfb_photos[] parameter. An attacker can exploit this by tricking an authenticated administrator into submitting a crafted request that traverses directories to access or manipulate files outside the intended upload directory.
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 PlusWordPress extension
< 1.6.2CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 installation and versionCheck if the buddypress-activity-plus plugin is installed in your WordPress environment and retrieve its installed version number from the plugin header or admin panelAffected if The installed version is less than 1.6.2
-
Confirm plugin is activeVerify that the buddypress-activity-plus plugin is currently activated on the WordPress site through the plugins admin pageAffected if The plugin is active and the version is below 1.6.2
-
Identify vulnerable AJAX endpointLocate the bpfb_remove_temp_images AJAX action handler in the plugin files, typically in the main plugin PHP file or an AJAX-handling moduleAffected if The bpfb_remove_temp_images AJAX action exists and handles the bpfb_photos[] parameter without proper validation
-
Check parameter handling for directory traversalExamine the code handling the bpfb_photos[] parameter in the bpfb_remove_temp_images action to verify if directory traversal prevention (such as basename() or path sanitization) is implementedAffected if The parameter is used directly in file operations without sanitization allowing ../ sequences to traverse directories
-
Confirm administrator session requirementUnderstand that exploitation requires a logged-in administrator to unknowingly submit a crafted request, meaning the attack surface exists if administrators use the pluginAffected if Administrators are authenticated and the vulnerable AJAX action is accessible to them
Your environment is affected if the buddypress-activity-plus plugin is installed, active, and running a version lower than 1.6.2 with the unprotected bpfb_remove_temp_images AJAX action handling the bpfb_photos[] parameter.
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 data1.6.2
Update the buddypress-activity-plus plugin to version 1.6.2 or later, which includes CSRF token validation and proper input sanitization for the bpfb_photos[] parameter to prevent directory traversal attacks.
Fix this in Buddypress Activity Plus
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-2015-9455 — 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-2015-9455 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