CVE-2016-9889
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 · uneditedSome forms with the parameter geo_zoomlevel_to_found_location in Tiki Wiki CMS 12.x before 12.10 LTS, 15.x before 15.3 LTS, and 16.x before 16.1 don't have the input sanitized, related to tiki-setup.php and article_image.php. The impact is XSS.
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 confidenceThis is a reflected XSS vulnerability in Tiki Wiki CMS where forms with the parameter 'geo_zoomlevel_to_found_location' in tiki-setup.php and article_image.php do not properly sanitize user input before reflecting it back in 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= 12.0= 12.1= 12.2= 12.3= 12.4= 12.5= 12.6= 12.7= 12.8= 12.9= 15.0= 15.1CVSS 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 Tiki Wiki CMS versionCheck the version file (typically version.php in the root directory) or access the admin panel and look for the version information under 'Admin' > 'System' or similarAffected if The installed version is 12.0-12.9, 15.0, or 15.1
-
Confirm affected version rangeCompare your installed version against the affected list: 12.x versions (12.0 through 12.9) and 15.x versions (15.0, 15.1)Affected if The version matches any of the affected versions listed
-
Locate vulnerable script filesCheck if tiki-setup.php and article_image.php exist in your Tiki installation root directoryAffected if These files exist and are accessible via web requests
-
Test vulnerable parameter reflectionSend a crafted request to tiki-setup.php or article_image.php with the parameter geo_zoomlevel_to_found_location=<script>alert(1)</script> and examine if the script tag is reflected unsanitized in the responseAffected if The parameter value is reflected in the HTML response without proper encoding or sanitization
You are affected if your Tiki Wiki CMS version is 12.0-12.9, 15.0, or 15.1 AND the geo_zoomlevel_to_found_location parameter is reflected in responses without 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 the vendor patches (12.10 LTS, 15.3 LTS, 16.1) or implement proper input validation/sanitization for the geo_zoomlevel_to_found_location parameter in the affected files.
- 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-2016-9889 — 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-2016-9889 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