CVE
BuddyPress authorization bypass in component settings update
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
BuddyPress, a WordPress plugin, has an improper authorization flaw in its component settings update function that affects all versions up to and including 14.4.0. An attacker with Author-level access or higher can reach it remotely over the network and use it to turn plugin components on or off.
Original description
The BuddyPress plugin for WordPress is vulnerable to unauthorized modification of data due to a misconfigured capability check on the 'update_item_permissions_check' function in all versions up to, and including, 14.4.0. This makes it possible for authenticated attackers, with Author-level access and above, to enable and disable plugin components.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.3/10CVSS 4.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-1209 (BuddyPress <= 14.4.0 - Improper Authorization to Authenticated (Author+) Component Settings Update), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-1209 (entry last updated 2026-11-18):
Affected:
- buddypress BuddyPress: through 14.4.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-1209 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-1209 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/b24143b1-1c3c-4d8e-9887-36f050de9b8c?source=cve
- https://plugins.trac.wordpress.org/browser/buddypress/tags/14.4.0/bp-core/classes/class-bp-rest-components-endpoint.php#L273
- https://plugins.trac.wordpress.org/browser/buddypress/tags/14.4.0/bp-core/classes/class-bp-rest-components-endpoint.php#L171
- https://plugins.trac.wordpress.org/changeset/3599376/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-1209
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-1209"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- buddypress BuddyPress
through 14.4.0
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-1209 |
| Record | NVD · CVE-2026-1209 |
| Other links 4 | |
| Link | wordfence.com · threat-intel/vulnerabilities/id/b24143b1-1c3c-4d8e-9887-36f050de9b8c?source=cve |
| Link | plugins.trac.wordpress.org · browser/buddypress/tags/14.4.0/bp-core/classes/class-bp-rest-components-endpoint.php#L273 |
| Link | plugins.trac.wordpress.org · browser/buddypress/tags/14.4.0/bp-core/classes/class-bp-rest-components-endpoint.php#L171 |
| Link | plugins.trac.wordpress.org · changeset/3599376 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-1209
Is CVE-2026-1209 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-1209?
BuddyPress: through 14.4.0.Source: cve.now feed data