CVE-2025-30845
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 webangon The Pack Elementor addons the-pack-addon allows PHP Local File Inclusion.This issue affects The Pack Elementor addons: from n/a through <= 2.1.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 · high confidenceLocal File Inclusion vulnerability in The Pack Elementor addons plugin allows attackers to include local PHP files due to improper control of filename parameters in include/require statements. This can lead to arbitrary code execution if an attacker can control which files are included.
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 The Pack plugin is installedCheck for the presence of 'the-pack' directory in wp-content/plugins/ on your WordPress file systemAffected if The plugin directory exists in the plugins folder
-
Determine installed versionOpen the main plugin file (typically the-pack/index.php or the-pack/the-pack.php) and locate the version number in the plugin header commentAffected if The version number matches or precedes the vulnerable version range
-
Confirm plugin is activeLog into WordPress admin and navigate to Plugins > Installed Plugins, or query the wp_options table for option_name='active_plugins'Affected if The Pack appears in the list of active plugins
-
Check for exploitation indicatorsReview web server access logs for patterns like '../' directory traversal in requests to plugin files, particularly in parameters that might be used in include/require statementsAffected if Suspicious directory traversal patterns are found in access logs targeting the plugin
-
Audit vulnerable code patternsIf you have file system access, search plugin PHP files for include/require statements using uncontrolled variables (e.g., include($some_var); or require($_GET['file']);)Affected if Unsanitized variable usage is found in include/require statements within the plugin code
Your environment is affected if The Pack Elementor addons plugin is installed, active, and running a vulnerable version where the code contains unsanitized filename parameters in include/require statements.
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 The Pack Elementor addons to the latest patched version. If no patch is available, disable the plugin or implement web application firewall rules to block directory traversal patterns in request parameters.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30845 — 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-30845 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