CVE-2017-14070
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 · uneditedCross Site Scripting (XSS) exists in NexusPHP 1.5.beta5.20120707 via the PATH_INFO to ipsearch.php, related to PHP_SELF.
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 confidenceA reflected Cross Site Scripting (XSS) vulnerability exists in NexusPHP 1.5.beta5.20120707 within ipsearch.php. The vulnerability stems from improper sanitization of the PATH_INFO variable, which is related to the PHP_SELF superglobal. An attacker can inject malicious JavaScript code through the URL path, which gets executed in the victim's browser when the crafted URL is visited.
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= 1.5CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Confirm NexusPHP installationLocate the NexusPHP installation directory on the web server. Look for the main index.php or common NexusPHP files (such as config.php) to verify the application is present.Affected if The NexusPHP application directory is found on the server.
-
Identify installed NexusPHP versionCheck the version file, changelog, or any version identifier within the NexusPHP installation. Common locations include a VERSION file, the codebase header comments, or the config.php file.Affected if The installed version matches 1.5.
-
Verify ipsearch.php existsLocate the ipsearch.php file within the NexusPHP web root or /inc directory. Confirm the file is accessible via the web server.Affected if The file ipsearch.php exists and is web-accessible.
-
Inspect ipsearch.php for vulnerable PATH_INFO usageOpen ipsearch.php in a text editor and examine the source code. Look for direct usage of PATH_INFO, $_SERVER['PATH_INFO'], or $_SERVER['PHP_SELF'] variables that are inserted into HTML output without htmlspecialchars() or equivalent encoding.Affected if The code uses PATH_INFO or PHP_SELF in HTML output without proper sanitization using htmlspecialchars() or similar functions.
-
Confirm URL-based XSS executionIf the vulnerable code pattern is found, note that visiting a crafted URL such as http://[target]/ipsearch.php/[malicious_script] would cause the browser to execute the injected JavaScript.Affected if The PATH_INFO variable is reflected in the page output without encoding, enabling reflected XSS.
A user is affected if NexusPHP version 1.5 is installed, the ipsearch.php file exists, and the source code uses PATH_INFO or PHP_SELF in HTML output without htmlspecialchars() sanitization.
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 using htmlspecialchars() or equivalent functions to all user-controllable input derived from PHP_SELF and PATH_INFO before rendering in HTML. Additionally, validate and sanitize the PATH_INFO variable at the point of input.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14070 — 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-2017-14070 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