dbcve.org
Allow Php ExecuteWordPress extension · Sksdev

CVE-2024-13890

HIGH · 7.2 CVSS v3.1 Published 2025-03-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 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.

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 Allow PHP Execute plugin for WordPress up to version 1.0 contains a PHP code injection vulnerability that allows authenticated users with Editor-level access or higher to execute arbitrary PHP code by inserting it into posts or pages. This occurs because the plugin permits PHP code entry without proper sanitization for users who have unfiltered HTML permissions.

MitigationImmediately disable or remove the Allow PHP Execute plugin, or update to a patched version once available. Review user roles and permissions to restrict who can edit content, and audit recently modified posts/pages for malicious PHP code.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Allow Php ExecuteWordPress extension
Affected:= 1.0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify if the Allow PHP Execute plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Sksdev Allow Php Execute' or 'Allow PHP Execute' in the plugin list. Note whether it is active or inactive.
    Affected if The plugin is present and active in the WordPress installation
  2. Verify the installed version
    On the Plugins page, click on the plugin name or view details to see the version number. Confirm it is version 1.0.
    Affected if The installed version is 1.0
  3. Check user roles with unfiltered_html capability
    Use a user role editor plugin or query the wp_usermeta and wp_capabilities database tables to identify users with the unfiltered_html capability (typically Editors and Administrators by default).
    Affected if Any user account with Editor-level or higher access exists on the site
  4. Inspect posts and pages for PHP code
    Search the wp_posts table in the database or use WordPress admin to review recent posts and pages. Look for content containing <?php tags or suspicious code blocks within the post content field.
    Affected if Any post or page contains raw PHP code tags (<?php) in the content
  5. Check plugin configuration settings
    Look for plugin-specific settings pages under Settings or a dedicated Allow PHP Execute menu item in the WordPress admin sidebar. Examine if PHP code execution is enabled or configurable.
    Affected if PHP execution settings are configurable through the plugin interface

A user is affected if the Sksdev Allow Php Execute plugin version 1.0 is installed and active on the WordPress site with any user accounts having Editor-level access or higher.

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

Immediately disable or remove the Allow PHP Execute plugin, or update to a patched version once available. Review user roles and permissions to restrict who can edit content, and audit recently modified posts/pages for malicious PHP code.

Recommended fix High confidence

Version 1.1 or later (latest available version from WordPress plugin repository)

  1. Go to WordPress admin dashboard > Plugins > Installed Plugins
  2. Locate 'Allow PHP Execute' in the plugin list
  3. If an update is available, click 'Update Now' to install the latest version
  4. Alternatively, manually download the fixed version from the official WordPress plugin repository (plugins.trac.wordpress.org) and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify the plugin is functioning correctly and test that PHP code execution still works as intended for authorized users

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

Fix this in Allow Php Execute Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13890 — 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-13890 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