CVE-2024-49251
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 Acnoo Maan Addons For Elementor maan-elementor-addons allows Local Code Inclusion.This issue affects Maan Addons For Elementor: from n/a through <= 1.0.1.
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 · moderate confidenceA Local Code Inclusion vulnerability in Acnoo Maan Addons For Elementor plugin (versions <=1.0.1) allows attackers to include arbitrary local PHP files through improper control of filenames in include/require statements. This stems from insufficient input validation on parameters used in PHP file inclusion functions, potentially enabling arbitrary 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 if Acnoo Maan Addons For Elementor plugin is installedAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Maan Addons For Elementor' or 'Acnoo Maan Addons'Affected if The plugin appears in the installed plugins list
-
Determine the installed plugin versionIn the plugins list, click on the plugin details or view the plugin files to read the version number from the main PHP file header comment (typically comments contain 'Version: x.x.x')Affected if The version number is 1.0.1 or lower
-
Confirm the vulnerability exists in the codebaseReview the plugin PHP source code for file inclusion patterns (include, require, include_once, require_once) that use variables or request parameters without proper validation. Search for patterns like 'include($_REQUEST' or 'require($' in the plugin directoryAffected if The plugin code contains include/require statements using unvalidated user input from request parameters
-
Check if vulnerable endpoints are accessibleIdentify any publicly accessible AJAX actions or front-end endpoints registered by this plugin that accept filename parameters. Check wp-admin/admin-ajax.php and front-end routes for actions starting with 'maan_' or similarAffected if The plugin exposes endpoints that accept file path parameters without sanitization
The environment is affected if Acnoo Maan Addons For Elementor plugin version 1.0.1 or lower is installed and contains file inclusion code using unvalidated request parameters, especially if those endpoints are accessible to attackers.
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 dataUpgrade to a patched version of Maan Addons For Elementor when available. Until then, disable the plugin or implement strict allowlist-based input validation on any user-controllable parameters used in include/require statements.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49251 — 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-49251 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