Athemes Addons For ElementorWordPress extension · Athemes
CVE-2025-32158
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 Syed Balkhi aThemes Addons for Elementor athemes-addons-for-elementor-lite.This issue affects aThemes Addons for Elementor: from n/a through <= 1.1.3.
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 confidenceThis is a PHP Remote File Inclusion (RFI) vulnerability in the aThemes Addons for Elementor WordPress plugin (version <=1.1.3). The vulnerability allows attackers to include remote files via user-controlled input in PHP include/require statements, potentially leading to arbitrary code execution on the affected server.
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
Athemes Addons For ElementorWordPress extension
<= 1.0.16CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 the plugin is installedCheck for the presence of the aThemes Addons for Elementor plugin in the WordPress installation under wp-content/plugins/ directory, or use WP CLI: wp plugin list --name='athemes-addons-for-elementor'Affected if The plugin is found installed on the WordPress site
-
Determine the installed versionRead the version number from the plugin's main PHP file header (commonly main.php or index.php) in the athemes-addons-for-elementor folder under wp-content/plugins/, or use WP CLI: wp plugin get athemes-addons-for-elementor --format=jsonAffected if The reported version is less than or equal to 1.0.16 (or 1.1.3 depending on the accurate affected range)
-
Identify vulnerable include/require patternsSearch the plugin directory for PHP files containing include, include_once, require, or require_once statements that use variables in the file path without proper sanitization (e.g., include($_GET['file']); or include($path);)Affected if Files containing dynamic include/require statements with unsanitized user input are found in the plugin
-
Check for exposed admin endpointsReview the plugin's admin menu registration and AJAX handlers in the plugin's main file to identify if any endpoints accept file path parameters without validationAffected if The plugin exposes admin or AJAX endpoints that accept file path parameters used in include/require statements
A site is affected if aThemes Addons for Elementor is installed with version 1.0.16 or lower and contains PHP include/require statements that use unsanitized user input, allowing remote file inclusion.
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 to the latest version of aThemes Addons for Elementor as soon as a patch is released. If immediate patching is not possible, consider disabling the plugin or implementing web application firewall rules to block malicious file inclusion attempts.
Fix this in Athemes Addons For Elementor
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32158 — 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-2025-32158 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