sales@hackhalt.com

Home / Threats / CVE-2026-88912

rtMedia for WordPress, BuddyPress and bbPress - Security Vulnerability (CVE-2026-88912)

CVE-2026-88912

The rtMedia for WordPress, BuddyPress and bbPress WordPress plugin before 4.7.12 does not check ownership before changing the privacy level of an activity and its attached media, relying only on a nonce shared with every logged-in user, allowing users with a subscriber-level account or above to make another user's private activity public or hide it.

CVE-2026-88912

MEDIUM CVSS 4.2 Published 2026-09-13 Updated 2026-09-14
AI Risk Moderate (38/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P4 Planned
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
Affected Components 1
Reference Links 1
AI Risk Engine Moderate (38/100)
Exploitability Low
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-09-13 CVE published and first recorded in the threat feed.
  2. 2026-09-14 Record updated with latest vulnerability metadata.
  3. 2026-09-21 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 44 days ago

AI enriched 44 days ago (2026-09-21 17:51 UTC)

Technical Summary

The rtMedia for WordPress, BuddyPress and bbPress WordPress plugin before 4.7.12 does not check ownership before changing the privacy level of an activity and its attached media, relying only on a nonce shared with every logged-in user, allowing users with a subscriber-level account or above to make another user's private activity public or hide it.

Potential Impact

Severity is MEDIUM (CVSS 4.2). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Low based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 38/100 (Moderate, Low) with priority P4 Planned. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

References

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update rtMedia for WordPress, BuddyPress and bbPress to 4.7.12 or later.

That is the complete fix. Everything below is what protects you in the meantime.

No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.

Start free

Not sure if you are affected?

Scan your site to see whether it runs rtMedia for WordPress, BuddyPress and bbPress, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs rtMedia for WordPress, BuddyPress and bbPress. Versions below 4.7.12 are vulnerable; that release and later are not. An attacker needs any registered account, so open registration materially increases the risk.

How do I fix it?

Update rtMedia for WordPress, BuddyPress and bbPress to version 4.7.12 or later. That is the complete fix.