dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-11023

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Inclusion of Functionality from Untrusted Control Sphere, Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ArkSigner Software and Hardware Inc. AcBakImzala allows PHP Local File Inclusion. This issue affects AcBakImzala: before v5.1.4.

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 confidence

AcBakImzala before v5.1.4 contains a PHP Local File Inclusion (LFI) vulnerability where the application improperly controls filenames used in include/require statements. This allows authenticated or unauthenticated attackers to read sensitive files from the server filesystem or potentially achieve remote code execution by including malicious local files.

MitigationUpgrade to AcBakImzala v5.1.4 or later. Until patched, disable allow_url_include in PHP configuration and implement strict whitelist-based input validation on all file inclusion paths.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify AcBakImzala installation
    Search the web server document root for AcBakImzala files (index.php, config files) or check for 'AcBakImzala' string in page source/headers
    Affected if AcBakImzala is present on the server and accessible via web
  2. Determine installed version
    Open version file or admin page that displays the software version, or grep for version strings in PHP source files
    Affected if Version is below 5.1.4 (e.g., 5.1.3, 5.0.x, etc.)
  3. Identify file inclusion parameters
    Review PHP source code for include, require, include_once, or require_once statements that use $_GET, $_POST, or $_REQUEST variables directly in the path
    Affected if Code uses user-supplied input in include/require without validation (e.g., include($_GET['page']) )
  4. Check application exposure
    Determine if the application is accessible from untrusted networks or the internet via HTTP/HTTPS
    Affected if The vulnerable file inclusion endpoints are reachable without authentication or from external networks
  5. Verify file readability
    Attempt to read a known file via the suspected LFI parameter (e.g., ?file=../../../../etc/passwd) using a test request
    Affected if The server returns file contents instead of an error, indicating LFI is exploitable

The environment is affected if AcBakImzala version is below 5.1.4 AND the application exposes file inclusion functionality using user input without validation to the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to AcBakImzala v5.1.4 or later. Until patched, disable allow_url_include in PHP configuration and implement strict whitelist-based input validation on all file inclusion paths.

Recommended fix Moderate confidence

v5.1.4

  1. 1. Create a complete backup of the current AcBakImzala installation, including all configuration files and data directories.
  2. 2. Download the fixed version v5.1.4 from the official vendor source (ArkSigner Software and Hardware Inc.).
  3. 3. Stop any running services or processes related to AcBakImzala before applying the update.
  4. 4. Replace the existing AcBakImzala installation files with the new v5.1.4 files, preserving configuration files where possible.
  5. 5. Review and restore any custom configurations that may have been overwritten during the file replacement.
  6. 6. Restart the AcBakImzala services.
  7. 7. Verify the installation was successful by checking the application version and confirming the PHP file inclusion vulnerability is no longer present.
  8. 8. Test critical functionality to ensure the upgrade did not break existing workflows.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11023 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11023 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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