CVE-2025-69383
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 Agence web Eoxia - Montpellier WP shop wpshop allows PHP Local File Inclusion.This issue affects WP shop: from n/a through <= 2.6.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 PHP Local File Inclusion (LFI) vulnerability in the WP shop WordPress plugin allows attackers to include arbitrary PHP files from the server due to improper control of filename for include/require statements. This can lead to remote code execution if attackers can upload or control files on the server.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 WP shop plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP shop' or check the filesystem at /wp-content/plugins/ for a folder named 'wp-shop' or similarAffected if The WP shop plugin is present on the WordPress installation
-
Determine installed WP shop versionCheck the plugin's main PHP file header for 'Version:' comment, or in WordPress admin go to Plugins > Installed Plugins and find the version number listed for WP shopAffected if The installed version matches or falls within an affected version range (if known); if version is unknown, assume affected if plugin is present and unpatched
-
Identify file inclusion endpointsSearch plugin source code for include, require, include_once, or require_once statements that use variables in the file path (e.g., include($file), require($_GET['file']))Affected if The plugin contains dynamic file inclusion using uncontrolled input without proper sanitization
-
Check web server access to plugin filesAttempt to access common file inclusion parameter names via GET/POST requests to plugin pages (e.g., ?file=../../../wp-config.php)Affected if The server allows path traversal through plugin parameters and returns file contents or includes them
-
Audit uploaded files for malicious PHPInspect /wp-content/uploads/ and plugin directories for unexpected .php files with suspicious content or unusual timestampsAffected if There are uploaded PHP files that attackers could target for inclusion to achieve remote code execution
A user is affected if the WP shop plugin is installed and contains the LFI vulnerability where file inclusion parameters accept unsanitized user input that can be exploited to include arbitrary files.
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 WP shop to the latest version. If no patch is available, disable the plugin, implement strict input validation/whitelisting on file inclusion parameters, and ensure proper web server configuration to prevent unauthorized file access.
- 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-69383 — 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-69383 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