CVE-2024-5574
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 · uneditedThe WP Magazine Modules Lite plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.1.2 via the 'blockLayout' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
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 confidenceThe WP Magazine Modules Lite WordPress plugin up to version 1.1.2 is vulnerable to Local File Inclusion via the 'blockLayout' parameter. Authenticated attackers with Contributor-level access or higher can supply malicious file paths to include and execute arbitrary server-side files, including PHP code. This allows complete bypass of access controls and remote code execution when combined with upload capabilities.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin is installedCheck the WordPress plugin directory for 'wp-magazine-modules-lite' or check via wp-cli: wp plugin list --search='magazine-modules'Affected if The plugin is installed and active in WordPress
-
Determine installed versionCheck the plugin's main PHP file header for 'Version:' or use wp-cli: wp plugin get wp-magazine-modules-lite --field=versionAffected if Version is 1.1.2 or lower (any version up to and including 1.1.2)
-
Identify Contributor-level or higher usersList users with Contributor, Author, Editor, or Administrator roles via WordPress admin or wp-cli: wp user list --role=contributor --fields=user_login,rolesAffected if Any authenticated user with Contributor-level access or higher exists in the system
-
Inspect for vulnerable endpoint usageReview HTTP access logs for requests to the plugin's frontend rendering that include 'blockLayout' parameter (e.g., pattern: blockLayout=../ or blockLayout=/etc/passwd)Affected if Suspicious requests containing path traversal sequences are found in logs targeting the blockLayout parameter
You are affected if the WP Magazine Modules Lite plugin is installed with version 1.1.2 or lower and any Contributor-level or higher user accounts exist in the WordPress environment.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate WP Magazine Modules Lite to version 1.1.3 or later. If unable to update immediately, restrict Contributor-level user permissions and disable the plugin until a patch can be applied.
Version 1.1.3 or later (upgrade to the latest available version from wordpress.org)
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate WP Magazine Modules Lite
- Check if the current version is 1.1.2 or below
- If vulnerable, update the plugin to the latest available version
- Verify the update was successful and the new version is active
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5574 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5574 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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