# CVE-2024-4662: Oxygen Builder <= 4.8.2 - Authenticated (Contributor+) Remote Code Execution

> Authenticated contributors can inject arbitrary PHP code via post metadata in Oxygen Builder, leading to remote code execution and privilege escalation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 23 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-g37v-c843-6cw3

## What is CVE-2024-4662?

CVE-2024-4662 is a high-severity code injection vulnerability in Oxygen Builder, published on 23 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Oxygen Builder plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.8.2 via post metadata. This is due to the plugin storing custom data in post metadata without an underscore prefix. This makes it possible for lower privileged users, such as contributors, to inject arbitrary PHP code via the WordPress user interface and gain elevated privileges.

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

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


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

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

## Is CVE-2024-4662 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4662 is a high-severity code injection vulnerability in Oxygen Builder, published on 23 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4662 in the wild and no public exploit code.

Affected product: Oxygen Builder. 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-4662/ (Markdown: https://insights.sbomify.com/CVE-2024-4662/index.md)
```

## Sources

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

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