rtMedia for WordPress, BuddyPress and bbPress < 4.7.12 - Authenticated (Subscriber+) Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 4.7.12
- Affected Plugin
- rtMedia for WordPress, BuddyPress and bbPress
- Affected Version
< 4.7.12- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-88912
At a glance
CVE-2026-88912 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the rtMedia for WordPress, BuddyPress and bbPress WordPress plugin, affecting versions < 4.7.12. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.7.12; sites on affected versions should update now. Disclosed September 2026, reported by JunHee CHO.
Vulnerability Overview
The rtMedia for WordPress, BuddyPress and bbPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to 4.7.12. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform an unauthorized action.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in rtMedia for WordPress, BuddyPress and bbPress < 4.7.12 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For rtMedia for WordPress, BuddyPress and bbPress the fix is 4.7.12: builds < 4.7.12 are affected, anything from 4.7.12 onward is not.
Remediation
Update to version 4.7.12, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: rtMedia for WordPress, BuddyPress and bbPress 4.7.12 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in rtMedia for WordPress, BuddyPress and bbPress
- 9.8rtMedia for WordPress, BuddyPress and bbPress Arbitary File Upload
- 9.8rtMedia for WordPress, BuddyPress and bbPress < 3.7.40 SQL Injection
- 9.8rtMedia for WordPress, BuddyPress and bbPress <= 3.9.5 LFI
- 8.8CVE-2024-3293: rtMedia for WordPress SQL Injection
CVE-2024-3293 - 8.8CVE-2023-5931: rtMedia for WordPress Arbitrary File Upload
CVE-2023-5931 - 7.5CVE-2026-16482: rtMedia for WordPress SQL Injection
CVE-2026-16482 - 7.5CVE-2026-66592: rtMedia for WordPress SQL Injection
CVE-2026-66592 - 7.5CVE-2026-59549: rtMedia for WordPress SQL Injection
CVE-2026-59549
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C