dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-3352

HIGH · 7.2 CVSS v3.1 Published 2026-03-07
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 Easy PHP Settings plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 1.0.4 via the `update_wp_memory_constants()` method. This is due to insufficient input validation on the `wp_memory_limit` and `wp_max_memory_limit` settings before writing them to `wp-config.php`. The `sanitize_text_field()` function used for sanitization does not filter single quotes, allowing an attacker to break out of the string context in a PHP `define()` statement. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject and execute arbitrary PHP code on the server by modifying `wp-config.php`, which is loaded on every page request.

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 Easy PHP Settings WordPress plugin (versions up to 1.0.4) has a PHP Code Injection vulnerability in the update_wp_memory_constants() method. The plugin fails to properly escape single quotes when writing wp_memory_limit and wp_max_memory_limit values to wp-config.php via define() statements, allowing authenticated administrators to inject arbitrary PHP code.

MitigationUpdate to a patched version of the plugin once available. As an immediate workaround, restrict administrator-level access and manually review wp-config.php for any suspicious define() statements.

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
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 Easy PHP Settings plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'easy-php-settings' or similar. Look for the main plugin PHP file and check the declared version in the plugin header comment.
    Affected if The plugin is present in the plugins directory with a version of 1.0.4 or earlier.
  2. Confirm the plugin version
    Open the main plugin file (typically easy-php-settings.php or similar in the plugin folder) and locate the 'Version:' field in the plugin header. Compare this version number to 1.0.4.
    Affected if The declared version is 1.0.4 or any version up to and including 1.0.4.
  3. Check if the plugin is active
    In the WordPress admin dashboard, navigate to Plugins > Installed Plugins and verify whether Easy PHP Settings shows as 'Active', or query the wp_options table for the option_name 'active_plugins' to see if the plugin is enabled.
    Affected if The plugin is installed AND activated on the WordPress site.
  4. Inspect wp-config.php for suspicious define statements
    Open the wp-config.php file in the WordPress root directory and search for define() statements containing 'wp_memory_limit' or 'wp_max_memory_limit'. Examine the values passed to these define() calls for unescaped single quotes, unexpected PHP code, or base64-encoded content.
    Affected if The wp-config.php file contains define('wp_memory_limit', ...) or define('wp_max_memory_limit', ...) statements where the value contains unescaped single quotes, suspicious function calls, or arbitrary PHP syntax.
  5. Review recent modifications to wp-config.php
    Check the file modification timestamp of wp-config.php and compare it to expected changes. Look for recent additions or modifications to memory_limit related define() statements that were not intentionally made by an administrator.
    Affected if The wp-config.php file has recent modifications to memory-related define() statements that were not explicitly authorized.

You are affected if the Easy PHP Settings plugin versions up to 1.0.4 is installed, active, and wp-config.php contains potentially malicious define() statements for wp_memory_limit or wp_max_memory_limit with unescaped characters or suspicious 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 to a patched version of the plugin once available. As an immediate workaround, restrict administrator-level access and manually review wp-config.php for any suspicious define() statements.

Recommended fix Moderate confidence

Easy PHP Settings version 1.0.5 or later

  1. Identify the Easy PHP Settings plugin in the WordPress installation
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate Easy PHP Settings and check the current version (should be 1.0.4 or below)
  4. Update the plugin to the latest available version from the WordPress plugin repository
  5. Verify the update was successful and the new version is installed
  6. Review wp-config.php to ensure no malicious code was injected during the attack
  7. If compromised, restore wp-config.php from a clean backup

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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