Skip to content
Web

CVE-2026-105892

9.8
Critical
EPSS 0.42%Patch availableOct 13, 2026

Path traversal in rtMedia WordPress plugin allows arbitrary file access/deletion

common questions

Is CVE-2026-105892 being exploited?

Not confirmed. CVE-2026-105892 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.

How severe is CVE-2026-105892?

CVE-2026-105892 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-105892?

Yes. A fix has been recorded for CVE-2026-105892. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-105892 affect?

CVE-2026-105892 affects rtMedia for WordPress, rtMedia for BuddyPress, rtMedia for bbPress, rtMedia <= 4.7.13, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-105892?

Update rtMedia to fixed version immediately; if unavailable, disable plugin and audit affected sites.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
rtMedia for WordPressrtMedia for BuddyPressrtMedia for bbPressrtMedia <= 4.7.13WordPress sites using rtMedia plugin
impact

Path traversal permits arbitrary file read and deletion on web hosts, enabling data exposure, site loss/defacement, or potential site takeover.

action required

Immediate action required

affected versions
rtCamp Inc. rtMedia for WordPress, BuddyPress and bbPress
  • affected<= 4.7.13

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free