dbcve.org
Change Memory LimitWordPress extension · Simon99

CVE-2024-1093

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Change Memory Limit plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the admin_logic() function hooked via admin_init in all versions up to, and including, 1.0. This makes it possible for unauthenticated attackers to update the memory limit.

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 Change Memory Limit WordPress plugin lacks authorization checks on its admin_logic() function hooked via admin_init, allowing unauthenticated users to modify the PHP memory limit setting. An attacker could set extremely high memory limits to cause denial of service or exploit server resources.

MitigationUpdate the plugin to version 1.1 or later which includes capability verification. Until patched, consider removing the plugin or restricting access to wp-admin via firewall rules.

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
Change Memory LimitWordPress 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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. Verify the plugin is installed
    Check the WordPress plugins directory for the 'change-memory-limit' folder, or query the wp_options table for the active_plugins entry
    Affected if The Simon99 Change Memory Limit plugin folder exists in /wp-content/plugins/ or is listed in active WordPress plugins
  2. Confirm the vulnerable version
    Open the main plugin file (change-memory-limit.php) and locate the version comment header, or check the WordPress plugin repository version
    Affected if The installed version is exactly 1.0 (no patch version applied)
  3. Inspect the admin_logic function
    Open the plugin PHP file and locate the admin_logic() function - verify it is hooked via add_action('admin_init', 'admin_logic') without any capability checks
    Affected if The admin_logic function lacks current_user_can() or similar authorization checks before executing memory limit modification logic
  4. Test unauthenticated access to admin_init
    Send a crafted request to wp-admin/admin.php?page=change_memory_limit (or the plugin's admin page) without logging in, attempting to modify the memory limit parameter
    Affected if The request succeeds and the PHP memory_limit setting is modified without authentication credentials
  5. Check current PHP memory_limit value
    Run php -i or check the PHP memory_limit value via WordPress admin, or inspect .htaccess/php.ini for unusual high memory limit values
    Affected if The memory_limit is set to an abnormally high value (e.g., 512M, 1G, or higher) that was not intentionally configured by the administrator

The environment is affected if the Simon99 Change Memory Limit plugin version 1.0 is installed and the admin_logic function can be accessed or executed without authentication, allowing unauthorized modification of the PHP memory_limit setting.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.1 or later which includes capability verification. Until patched, consider removing the plugin or restricting access to wp-admin via firewall rules.

Fix this in Change Memory Limit Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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