CVE-2017-12777
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 version v1.5 via some parameter to usersearch.php.
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 confidenceCross-Site Scripting (XSS) vulnerability in NexusPHP v1.5 where user-supplied input to the usersearch.php page is not properly sanitized or output-encoded, allowing injection of malicious HTML/JavaScript into the response.
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 installation and locate usersearch.phpSearch for the file 'usersearch.php' in the web root directory of the application.Affected if The file usersearch.php exists in the web application directory.
-
Verify NexusPHP version is 1.5Check the version identifier in NexusPHP (typically in a version file, README, or the main index page). Compare against the affected version range of = 1.5.Affected if The installed NexusPHP version is exactly 1.5.
-
Inspect usersearch.php for user input handlingOpen usersearch.php and locate where GET or POST parameters are processed and reflected in the HTML output.Affected if The code processes user-supplied parameters without sanitization functions.
-
Check for missing output encodingSearch the usersearch.php file for use of htmlspecialchars, htmlentities, or similar output encoding functions on user input parameters.Affected if User input parameters are output directly into HTML without htmlspecialchars or equivalent encoding.
-
Identify vulnerable parameter reflection pointsExamine the code between input receipt and HTML output to find where user-supplied values are inserted into the page response without sanitization.Affected if User-supplied parameters are reflected in the HTML response without proper sanitization.
The environment is affected if NexusPHP version 1.5 is installed and usersearch.php reflects user input without htmlspecialchars or equivalent output encoding.
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 proper input validation and output encoding (e.g., htmlspecialchars) to all user-supplied parameters in usersearch.php before reflecting them in HTML output.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12777 — 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-12777 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