# CVE-2026-12906: RTMKit Addons for Elementor < 2.0.9 - Contributor+ Private Post Title Disclosure

> Contributors can read titles of private, draft, and trashed posts due to missing capability checks in an AJAX action.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-344h-fqfm-3mrj

## What is CVE-2026-12906?

CVE-2026-12906 is a low-severity missing authorization vulnerability in Unknown RTMKit, published on 16 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-12906?


## How do I fix CVE-2026-12906?

No fix has been published for CVE-2026-12906 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-12906 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12906 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12906 and fix it if it is affected.

What it is: CVE-2026-12906 is a low-severity missing authorization vulnerability in Unknown RTMKit, published on 16 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12906 exists.

Affected product: Unknown RTMKit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-12906/ (Markdown: https://insights.sbomify.com/CVE-2026-12906/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-12906
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-12906
- OSV: https://osv.dev/vulnerability/CVE-2026-12906

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-12906/
Summaries are generated and may contain mistakes; the official description above is the record.