Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-9218: CWE-862 Missing Authorization in rtcamp rtMedia for WordPress, BuddyPress and bbPress

0
Low
VulnerabilityCVE-2025-9218cvecve-2025-9218cwe-862
Published: Sat Dec 13 2025 (12/13/2025, 04:31:26 UTC)
Source: CVE Database V5
Vendor/Project: rtcamp
Product: rtMedia for WordPress, BuddyPress and bbPress

Description

The rtMedia for WordPress, BuddyPress and bbPress plugin for WordPress is vulnerable to to Information Disclosure due to missing authorization in the handle_rest_pre_dispatch() function when the Godam plugin is active, in versions 4.7.0 to 4.7.3. This makes it possible for unauthenticated attackers to retrieve media items associated with draft or private posts.

AI-Powered Analysis

AILast updated: 12/20/2025, 06:18:27 UTC

Technical Analysis

CVE-2025-9218 is a vulnerability identified in the rtMedia plugin versions 4.7.0 through 4.7.3, which integrates with WordPress, BuddyPress, and bbPress platforms. The vulnerability stems from a missing authorization check within the handle_rest_pre_dispatch() function, specifically when the Godam plugin is active. This missing authorization allows unauthenticated attackers to retrieve media items associated with draft or private posts, which are normally restricted. The vulnerability is classified under CWE-862 (Missing Authorization) and results in information disclosure, compromising the confidentiality of media content. The attack vector is network-based (remote), requires no privileges or user interaction, but has high attack complexity, likely due to the need for specific plugin configurations and knowledge of the target environment. The CVSS v3.1 base score is 3.7, reflecting a low severity primarily due to limited impact scope and exploitation difficulty. No integrity or availability impacts are noted. No patches are currently linked, and no known exploits have been reported in the wild. The vulnerability affects a niche plugin ecosystem but could expose sensitive media content, especially in environments where draft or private posts contain confidential information. The presence of the Godam plugin is a prerequisite for exploitation, indicating a compound configuration risk. This vulnerability highlights the importance of proper authorization checks in REST API endpoints within WordPress plugins.

Potential Impact

For European organizations, the primary impact is unauthorized disclosure of media content linked to draft or private posts within WordPress sites using rtMedia alongside the Godam plugin. This could lead to leakage of sensitive or proprietary images, videos, or documents that were intended to remain confidential. Although the vulnerability does not affect data integrity or system availability, the exposure of confidential media could result in reputational damage, privacy violations, or compliance issues under GDPR if personal data is involved. Organizations relying on BuddyPress or bbPress for community or forum functionalities may be particularly at risk if they use rtMedia to manage media content. The low CVSS score and high attack complexity suggest a limited risk of widespread exploitation; however, targeted attacks against high-value sites remain possible. The absence of known exploits reduces immediate threat but does not eliminate future risk. European entities with public-facing WordPress installations should assess their plugin configurations to prevent inadvertent data exposure.

Mitigation Recommendations

1. Monitor the rtMedia plugin vendor’s official channels for security patches addressing CVE-2025-9218 and apply updates promptly once available. 2. Temporarily disable the Godam plugin if it is not essential, as its activation is a prerequisite for exploitation. 3. Conduct an audit of WordPress REST API endpoints and plugin configurations to ensure proper authorization controls are enforced, especially for media associated with draft or private posts. 4. Implement web application firewalls (WAFs) with custom rules to detect and block suspicious REST API requests targeting rtMedia endpoints. 5. Restrict access to WordPress REST API endpoints via IP whitelisting or authentication where feasible. 6. Review and minimize the use of draft or private posts containing sensitive media, or consider encrypting sensitive media files stored on the server. 7. Educate site administrators about the risks of enabling plugins without thorough security review, particularly those that interact with REST APIs. 8. Regularly back up WordPress sites and media content to enable recovery in case of compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-08-19T23:21:42.590Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693cef67d977419e584a5279

Added to database: 12/13/2025, 4:45:27 AM

Last enriched: 12/20/2025, 6:18:27 AM

Last updated: 2/6/2026, 9:09:56 PM

Views: 97

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats