CVE-2024-56282
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Elicus WPMozo Addons Lite for Elementor wpmozo-addons-lite-for-elementor allows PHP Local File Inclusion.This issue affects WPMozo Addons Lite for Elementor: from n/a through <= 1.1.0.
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 confidenceElicus WPMozo Addons Lite for Elementor plugin before version 1.1.0 contains a PHP Local File Inclusion vulnerability where improper control of filenames in include/require statements allows attackers to include arbitrary PHP files from the server, potentially leading to code execution.
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 WPMozo Addons Lite for Elementor is installedCheck your WordPress plugins directory or navigate to wp-admin > Plugins to confirm the plugin is present on the siteAffected if The plugin is installed and active on the WordPress site
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > WPMozo Addons Lite for Elementor and read the version number displayed, or inspect the plugin main file header for the Version fieldAffected if Version is below 1.1.0 (e.g., 1.0.9, 1.0.8, etc.)
-
Identify vulnerable include/require code pathsSearch plugin files for include/require statements using dynamic variables or user-controllable input without proper sanitization, typically in files within the plugin directoryAffected if Code contains include/require statements that use unsanitized request parameters or variables to construct file paths
-
Check for unauthenticated access to vulnerable endpointsReview the plugin routing or AJAX handlers to determine if the file inclusion code can be reached without authenticationAffected if The file inclusion functionality is accessible to unauthenticated users or low-privilege users
You are affected if WPMozo Addons Lite for Elementor is installed with a version prior to 1.1.0 and the vulnerable file inclusion code paths are present and accessible on your site
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.
From vendor dataUpdate WPMozo Addons Lite for Elementor to the latest patched version. If no update is available, disable the plugin and remove vulnerable code paths that permit unauthenticated file inclusion.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-56282 — 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-56282 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