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.
Published: 2026-07-16
Score: 2.7 Low
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The RTMKit plugin for WordPress, prior to version 2.0.9, has a missing capability check in one of its AJAX actions. As a result, users with at least the Contributor role can resolve a request‑supplied post identifier and obtain the titles of other users’ private, draft, pending, scheduled and trashed posts. This is an information‑disclosure flaw, allowing an attacker to leak sensitive post titles but not the full content of the posts. The weakness corresponds to CWE‑639, Inconsistent Authorization. The vulnerability does not enable code execution or privilege escalation, but it provides indirect insight into the site’s private content structure.

Affected Systems

All installations of the RTMKit WordPress plugin before version 2.0.9 are affected. Administrators should verify that any instance of the plugin on their sites runs an older release, as the fix was introduced in release 2.0.9.

Risk and Exploitability

The CVSS score of 2.7 indicates low severity, and the EPSS score of less than 1% reflects a very low likelihood of exploitation. The flaw is not listed in CISA’s KEV catalog. The likely attack vector is a crafted AJAX request that bypasses authorization checks; an attacker only needs to be a Contributor or higher to read the leaking titles. Because the attack does not expose post content, the impact is limited to title disclosure, but it could be combined with other discovery techniques to assist in planning further attacks.

Generated by OpenCVE AI on July 31, 2026 at 02:16 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Install RTMKit plugin version 2.0.9 or later to restore proper capability checks
  • If an upgrade is not immediately possible, consider removing the Contributor role from users who should not see private drafts or use a role‑management plugin to limit visibility of titles for that role
  • Review and monitor server logs for anomalous AJAX requests that might indicate exploitation attempts

Generated by OpenCVE AI on July 31, 2026 at 02:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 16 Jul 2026 17:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-639
Metrics cvssV3_1

{'score': 2.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 16 Jul 2026 06:30:00 +0000

Type Values Removed Values Added
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.
Title RTMKit Addons for Elementor < 2.0.9 - Contributor+ Private Post Title Disclosure
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-07-16T16:53:35.525Z

Reserved: 2026-06-22T14:41:41.058Z

Link: CVE-2026-12906

cve-icon Vulnrichment

Updated: 2026-07-16T16:52:33.061Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-31T02:30:05Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key