# CVE-2026-5137: RTMKit <= 2.0.7 - Authenticated (Contributor+) Limited Local File Inclusion via 'template' Parameter

> Authenticated attackers with Contributor access can execute arbitrary PHP code via local file inclusion in the RTMKit WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-9g8c-cjxj-24g2

## What is CVE-2026-5137?

CVE-2026-5137 is a medium-severity path traversal vulnerability in rometheme RTMKit, published on 3 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The RTMKit (rometheme-for-elementor) plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 2.0.7 This is due to insufficient path validation on the 'template' parameter in the render_templates AJAX endpoint, which is used directly in a require/include statement without sanitization. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute files on the server ending in _templates.php, allowing the execution of any PHP code in those files.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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


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

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

## Is CVE-2026-5137 being exploited?

There is no known exploitation of CVE-2026-5137 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5137 is a medium-severity path traversal vulnerability in rometheme RTMKit, published on 3 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5137 in the wild and no public exploit code.

Affected product: rometheme 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-5137/ (Markdown: https://insights.sbomify.com/CVE-2026-5137/index.md)
```

## Sources

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

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