CVE-2017-1000428
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 · uneditedflatCore-CMS 1.4.6 is vulnerable to reflected XSS in user_management.php due to the use of $_SERVER['PHP_SELF'] to build links and a stored XSS in the admin log panel by specifying a malformed User-Agent string.
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 confidenceflatCore-CMS 1.4.6 contains two XSS vulnerabilities: a reflected XSS in user_management.php due to unsanitized use of $_SERVER['PHP_SELF'] in link construction, and a stored XSS in the admin log panel where malformed User-Agent strings are stored and rendered without sanitization.
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.4.6CVSS 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.
-
Identify flatCore CMS versionLocate the version file or footer in the flatCore installation. Check for a version.php file or inspect the main index page footer for the version number.Affected if The installed version is flatCore CMS 1.4.6.
-
Locate user_management.phpSearch the web root for the file user_management.php. If found, inspect the file and search for occurrences of $_SERVER['PHP_SELF'] within anchor tag href attributes.Affected if The file exists and contains unsanitized $_SERVER['PHP_SELF'] used in link construction without htmlspecialchars or equivalent encoding.
-
Check admin log panel accessLocate the admin log panel in the flatCore admin interface. This is typically found under admin settings or system logs. Determine if the panel displays User-Agent data.Affected if The admin log panel exists and renders User-Agent header values without sanitization.
-
Verify admin access requirementsDetermine whether the affected pages (user_management.php and admin log panel) are accessible only to authenticated administrators or if they require no authentication.Affected if An attacker can access these pages with admin privileges to trigger the XSS.
A user is affected if they are running flatCore CMS version 1.4.6 and have administrative access to the user_management.php page or admin log panel displaying User-Agent data.
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 to $_SERVER['PHP_SELF'] and implement proper input validation/sanitization for User-Agent header values before storing and displaying them in the admin log panel.
- 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-2017-1000428 — 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-1000428 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