dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-4662

HIGH · 8.8 CVSS v3.1 Published 2024-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Oxygen Builder WordPress plugin (versions up to 4.8.2) stores custom data in post metadata without an underscore prefix, which exposes this data in the standard WordPress post meta UI. This allows lower-privileged users like contributors to inject arbitrary PHP code through post metadata fields, enabling remote code execution and privilege escalation to administrator levels.

MitigationUpdate Oxygen Builder to version 4.8.2 or later. Review and restrict user capabilities for editing post metadata, and audit user accounts for any compromised elevated privileges.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Oxygen Builder is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Oxygen Builder' in the list. Alternatively, check the file /wp-content/plugins/oxygen/oxygen.php exists.
    Affected if Oxygen Builder plugin is installed and active
  2. Check Oxygen Builder version
    In WordPress admin Plugins list, click 'View Details' on Oxygen Builder to see the installed version number, or read the 'Version:' line from the oxygen.php file header.
    Affected if Installed version is 4.8.2 or lower (versions above 4.8.2 are fixed)
  3. Inspect post metadata for underscore-prefixed keys
    Query the wp_postmeta table for meta keys that lack an underscore prefix (e.g., SELECT meta_key FROM wp_postmeta WHERE meta_key NOT LIKE '\_%' ORDER BY meta_id DESC). These represent custom data exposed in the standard UI.
    Affected if Post meta entries exist without underscore prefix, indicating the vulnerable data exposure pattern
  4. Check for PHP code in post metadata values
    Search wp_postmeta values for patterns like '<?php', 'eval(', 'base64_decode', or shell execution functions. Use: SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE meta_value LIKE '%<?php%' OR meta_value LIKE '%eval(%'.
    Affected if Any post meta values contain PHP code or suspicious patterns, indicating active exploitation

You are affected if Oxygen Builder version 4.8.2 or lower is installed AND post metadata entries without underscore prefixes exist in the database, especially if they contain PHP code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Oxygen Builder to version 4.8.2 or later. Review and restrict user capabilities for editing post metadata, and audit user accounts for any compromised elevated privileges.

Recommended fix High confidence

Oxygen Builder 4.9 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Oxygen Builder plugin in the plugin list
  4. If an update is available, click 'Update Now' to update Oxygen Builder to the latest version
  5. Alternatively, navigate to Dashboard > Updates and select Oxygen Builder to update
  6. After updating, verify the plugin is running version 4.9 or higher by checking the plugin version in the installed plugins list
Caveat Review Oxygen Builder's changelog and test in a staging environment before updating production, as plugin updates may affect existing designs

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4662 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data