# CVE-2024-13890: Allow PHP Execute <= 1.0 - Authenticated (Editor+) PHP Code Injection

> Authenticated editors can inject PHP code into posts, leading to remote code execution on the WordPress site.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Mar 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qrc4-686m-f99j

## What is CVE-2024-13890?

CVE-2024-13890 is a high-severity code injection vulnerability in sksdev Allow PHP Execute, published on 8 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Allow PHP Execute plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 1.0. This is due to allowing PHP code to be entered by all users for whom unfiltered HTML is allowed. This makes it possible for authenticated attackers, with Editor-level access and above, to inject PHP code into posts and pages.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-13890?

It affects 1 product.


Products: Sksdev Allow Php Execute.

## How do I fix CVE-2024-13890?

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

## Is CVE-2024-13890 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13890 and fix it if it is affected.

What it is: CVE-2024-13890 is a high-severity code injection vulnerability in sksdev Allow PHP Execute, published on 8 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13890 in the wild and no public exploit code.

Affected product: sksdev Allow PHP Execute. 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-2024-13890/ (Markdown: https://insights.sbomify.com/CVE-2024-13890/index.md)
```

## Sources

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

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