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…
EPSS 0.3%top 78%

CVE-2026-12906: CWE-639 Authorization Bypass Through User-Controlled Key in RTMKit

0
Low
VulnerabilityCVE-2026-12906cvecve-2026-12906cwe-639
Published: 07/16/2026 (07/16/2026, 06:00:04 UTC)
Source: CVE Database V5
Product: RTMKit

Description

The RTMKit WordPress plugin before 2.0.9 does not perform a capability check in one of its AJAX actions and resolves a request-supplied post identifier directly, allowing users with at least the Contributor role to read the titles of other users' private, draft, pending, scheduled and trashed posts.

CVSS v3.1

Score 2.7low

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/16/2026, 06:32:46 UTC

Technical Analysis

The RTMKit WordPress plugin versions prior to 2.0.9 contain an authorization bypass vulnerability (CWE-639) due to missing capability checks in an AJAX action. This flaw permits users with at least Contributor privileges to access the titles of posts they should not normally view, including private, draft, pending, scheduled, and trashed posts belonging to other users. The vulnerability stems from the plugin directly using a user-supplied post identifier without verifying the user's permission to access that post.

Potential Impact

Users with Contributor role or higher can read the titles of other users' posts that are private, drafts, pending, scheduled, or trashed. This could lead to unauthorized disclosure of sensitive post metadata, potentially exposing information about unpublished or restricted content. There is no indication of code execution or data modification beyond reading post titles.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vulnerability affects versions before 2.0.9, upgrading to version 2.0.9 or later (if available) is recommended once confirmed. Until a patch is available, restrict Contributor role capabilities or disable the vulnerable AJAX action if possible.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
WPScan
Date Reserved
2026-06-22T14:41:41.058Z
Cvss Version
null
State
PUBLISHED
Remediation Level
null

Threat ID: 6a5877a968715ace4380686b

Added to database: 07/16/2026, 06:18:17 UTC

Last enriched: 07/16/2026, 06:32:46 UTC

Last updated: 08/30/2026, 03:00:10 UTC

Views: 81

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses