CVE-2026-25557
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 · uneditedEvoluted PHP Directory Listing Script through 4.0.5 contains a reflected cross-site scripting vulnerability in index.php where the dir parameter value is reflected without HTML encoding inside the HTML title element and inside anchor href attributes in the breadcrumb navigation. Attackers can inject arbitrary JavaScript via crafted dir parameter values by breaking out of the title context or injecting event handlers into breadcrumb anchor attributes to execute malicious scripts in a victim's browser.
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 · high confidenceEvoluted PHP Directory Listing Script through 4.0.5 has a reflected XSS in index.php where the 'dir' parameter is output without HTML encoding, allowing injection into the HTML title element and breadcrumb anchor href attributes.
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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
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.
-
Locate the Evoluted PHP Directory Listing Script installationSearch the web server for index.php that belongs to this script, typically in the document root. Look for files containing 'Evoluted' or 'Directory Listing' in comments/headers.Affected if The script is present on the server
-
Identify the installed versionOpen the main index.php file and search for a version string (e.g., 'version', '4.0.5', 'v.') in the code comments or configuration section near the top of the file.Affected if The version is 4.0.5 or lower (any version through 4.0.5)
-
Verify the dir parameter is processedSearch the index.php source code for occurrences of '$_GET' or '$_REQUEST' referencing 'dir' parameter, and confirm it is used in the page output.Affected if The dir parameter is read from the URL and included in the page output without validation
-
Confirm output encoding is missingExamine the code where the dir parameter value is output. Check if htmlspecialchars, htmlentities, or equivalent encoding is applied before rendering in the HTML title tag (<title>) and anchor href attributes in the breadcrumb section.Affected if The dir parameter value is output directly without htmlspecialchars or equivalent encoding
-
Test for live XSS (optional manual check)If you have access, request a URL such as /index.php?dir=test"><script>alert(1)</script> and inspect the page source to see if the script tag appears unescaped in the title or anchor href.Affected if The injected script tags or event handlers appear literally in the HTML source
You are affected if the Evoluted PHP Directory Listing Script version 4.0.5 or lower is installed and the dir parameter is processed without HTML encoding in the page output.
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 dataApply output encoding (htmlspecialchars with ENT_QUOTES) to the 'dir' parameter before rendering in the title element and anchor href attributes.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25557 — 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-2026-25557 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