CVE-2025-23945
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 Webliup Popliup popliup allows PHP Local File Inclusion.This issue affects Popliup: from n/a through <= 1.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 · moderate confidenceA PHP Local File Inclusion (LFI) vulnerability exists in Webliup Popliup version 1.1.1 and below. The application improperly validates user-supplied input used in include/require statements, allowing attackers to include arbitrary local PHP files by manipulating the filename parameter.
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.
-
Identify Webliup Popliup installationLocate the Popliup application files on the server - typically installed in a web-accessible directory. Check for the presence of index.php or main entry files from this application.Affected if The application is present and accessible via web requests.
-
Determine installed versionCheck version file, README, or any version metadata within the Popliup installation directory. Common locations include version.php, README.txt, or the main index.php header comments.Affected if The version is 1.1.1 or lower.
-
Locate file inclusion codeSearch the application source code for include, include_once, require, or require_once statements. Focus on files that handle request parameters, particularly any parameter named 'filename', 'file', 'page', or similar.Affected if User-controllable parameters are used directly in include/require statements.
-
Verify parameter accessibilityExamine the identified inclusion code to determine if the filename parameter comes from GET or POST requests and is not sanitized before being used in the include/require statement.Affected if The filename parameter can be controlled by external users without validation.
-
Check input validation implementationReview any existing validation or filtering logic around the file inclusion functionality. Look for allowlists, path sanitization, or prefix/suffix additions to the filename.Affected if No validation exists or validation can be bypassed.
You are affected if Webliup Popliup version 1.1.1 or below is installed and user-supplied filename parameters are used in include/require statements without proper validation.
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 dataImplement strict input validation using an allowlist approach for file inclusion paths, avoid using user input directly in include/require statements, and consider refactoring to use a defined set of allowed includes.
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23945 — 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-23945 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