CVE-2026-22325
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 · uneditedUnauthenticated Local File Inclusion in Promo <= 1.3.0 versions.
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 confidenceUnauthenticated Local File Inclusion vulnerability in the Promo WordPress plugin versions 1.3.0 and below allows remote attackers to read sensitive local files on the server without any authentication credentials by manipulating file path parameters.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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.
-
Identify Promo plugin versionLocate the plugin's version file, metadata, or admin interface version display. Common locations include plugin header comments in the main PHP file, a version.php file, or the plugin management interface.Affected if Installed version is 1.3.0 or lower
-
Locate the vulnerable componentIdentify the PHP file or endpoint that handles file inclusion within the Promo plugin. Look for functions that accept a file path as a parameter, such as include(), require(), or similar file loading functions.Affected if The file inclusion functionality exists and is accessible without authentication
-
Verify unauthenticated access is possibleAttempt to access the file inclusion endpoint without providing any authentication credentials. Check if the application processes the request without requiring login or session validation.Affected if The endpoint accepts and processes requests without any authentication token or session
-
Test for directory traversal vulnerabilitySend a crafted request to the file inclusion parameter containing path traversal sequences such as ../../../../etc/passwd or similar patterns to attempt to access files outside the intended directory.Affected if The application allows directory traversal sequences in the file parameter and returns file contents from the server file system
The environment is affected if the Promo plugin version is 1.3.0 or lower and the file inclusion endpoint is accessible without authentication.
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 Promo plugin to version greater than 1.3.0 or disable the plugin until a patched version is available; also implement web application firewall rules to block directory traversal patterns.
Latest version of Promo plugin (greater than 1.3.0)
- 1. Log in to your WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Find the 'Promo' plugin in the list
- 4. If an update is available, click 'Update Now' to upgrade to the latest version
- 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload via Plugins > Add New > Upload Plugin
- 6. After updating, verify the new version number reflects the patched release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22325 — 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-2026-22325 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