CVE-2025-22364
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 Service Shogun Ach Invoice App ach-invoice-app allows PHP Local File Inclusion.This issue affects Ach Invoice App: from n/a through <= 1.0.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 confidenceThis is a Local File Inclusion (LFI) vulnerability in the Service Shogun Ach Invoice App PHP application. The vulnerability allows attackers to manipulate file inclusion paths through improper validation of user-supplied input used in include/require statements, potentially enabling arbitrary PHP code execution.
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.
-
Identify if Ach Invoice App is installedSearch the web server document root for files or directories containing 'ach-invoice', 'shogun', or 'invoice' in the name, or look for PHP files that reference the application.Affected if The Ach Invoice App PHP application is present on the server.
-
Determine the installed versionCheck for a VERSION file, CHANGELOG, or any configuration file within the application directory that displays the software version. Compare against any available version information.Affected if The installed version is unpatched and lacks proper input validation for file inclusion operations.
-
Locate PHP files using dynamic includesSearch the application source code for include, require, include_once, or require_once statements that incorporate user-supplied parameters such as $_GET, $_POST, or $_REQUEST.Affected if The application uses dynamic file inclusion with unsanitized user input.
-
Inspect URL parameters for file path manipulationTest common file inclusion parameters (e.g., 'page', 'file', 'path', 'include', 'lang') in the application's URLs with directory traversal patterns like ../../etc/passwd.Affected if The application accepts and processes unsanitized file paths through URL parameters.
-
Review input validation in include/require logicExamine the PHP code handling file inclusion to determine if user input is validated, sanitized, or restricted to expected values before being used in include/require statements.Affected if User-supplied input is directly used in file inclusion operations without validation or path sanitization.
A user is affected if the Ach Invoice App is installed and its PHP code uses user-supplied input in include/require statements without proper validation, allowing path manipulation.
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 to a patched version of the Ach Invoice App that implements proper input validation and path sanitization for file inclusion operations, or deploy web application firewall rules to block directory traversal patterns.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22364 — 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-22364 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