dbcve.org
WebserverApplication · Easyphp

CVE-2023-3767

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-27
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
An OS command injection vulnerability has been found on EasyPHP Webserver affecting version 14.1. This vulnerability could allow an attacker to get full access to the system by sending a specially crafted exploit to the /index.php?zone=settings parameter.

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

EasyPHP Webserver 14.1 contains an OS command injection vulnerability in /index.php via the 'zone' parameter when set to 'settings'. Attackers can send specially crafted requests to inject and execute arbitrary operating system commands, potentially achieving full system compromise.

MitigationImplement strict input validation and sanitization on the 'zone' parameter to prevent command injection, or apply any available vendor patch. Consider isolating the webserver environment as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WebserverApplication
Affected:= 14.1

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. Confirm EasyPHP Webserver version
    Check installed software version - look for EasyPHP Webserver 14.1 in installed programs, or check the application directory for version indicators such as a 'version' file, about dialog, or version info in the main executable
    Affected if The installed version is exactly 14.1 (note: only version 14.1 is affected, other versions may not be vulnerable)
  2. Locate the vulnerable index.php file
    Search the EasyPHP installation directory for /index.php - typical paths may include C:\Program Files\EasyPHP\ or a custom install path\www\ or \htdocs\ subdirectories
    Affected if The file index.php exists in the webserver's document root and is accessible via HTTP
  3. Verify the webserver is running and accessible
    Check if the EasyPHP webserver service is running and attempt to access the main page at http://localhost or the configured port
    Affected if The webserver is running and the index.php page responds to requests
  4. Test for vulnerable parameter acceptance
    If the application is accessible, examine whether the 'zone' parameter is accepted - check if the URL accepts parameters like /index.php?zone=settings or similar patterns documented in the application's routing
    Affected if The application accepts a 'zone' parameter without visible input validation or sanitization being applied
  5. Inspect the index.php source code
    Review the index.php file content for how the 'zone' parameter is handled - look for direct use of the parameter in system calls, exec, shell_exec, passthru, or similar PHP functions
    Affected if The code passes the 'zone' parameter directly to PHP execution functions without sanitization

You are affected if EasyPHP Webserver version 14.1 is installed and running, the index.php file exists in the web-accessible directory, and the 'zone' parameter is processed by the application without command injection protection.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization on the 'zone' parameter to prevent command injection, or apply any available vendor patch. Consider isolating the webserver environment as a defense-in-depth measure.

Fix this in Webserver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3767 — 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-2023-3767 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