CVE-2018-5960
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 · uneditedZenario v7.1 - v7.6 has SQL injection via the `Name` input field of organizer.php or admin_boxes.ajax.php in the `Categories - Edit` module.
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 confidenceSQL injection vulnerability in Zenario CMS versions 7.1-7.6 allows attackers to inject malicious SQL queries through the Name input field in the Categories-Edit module via organizer.php or admin_boxes.ajax.php endpoints. User-supplied input is not properly sanitized before being used in SQL queries.
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= 7.1= 7.2= 7.3= 7.4= 7.5= 7.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 the installed Zenario CMS versionLocate the version file or admin panel footer that displays the Zenario CMS version numberAffected if the version number is 7.1, 7.2, 7.3, 7.4, 7.5, or 7.6
-
Verify access to the Categories-Edit moduleLog into the Zenario admin panel and navigate to the Categories-Edit functionality, or confirm the module is installed and enabledAffected if the Categories-Edit module is present and accessible in the admin interface
-
Confirm admin access to vulnerable endpointsVerify that you have authenticated admin access to organizer.php or admin_boxes.ajax.php by attempting to access these scripts directlyAffected if the server responds to requests at organizer.php or admin_boxes.ajax.php with admin session credentials
-
Inspect the Name input field in Categories-EditLocate the Name input field within the Categories-Edit interface and confirm it accepts user-supplied text without visible sanitization indicatorsAffected if the Name field accepts arbitrary input and appears to use the value directly in database operations
You are affected if your Zenario CMS version is between 7.1 and 7.6 inclusive, the Categories-Edit module is enabled, and you have admin access to the organizer.php or admin_boxes.ajax.php endpoints where the Name field is processed.
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 dataUpgrade to a patched version of Zenario or implement parameterized queries/prepared statements to sanitize all user input in the affected Categories-Edit module, particularly the Name field in both organizer.php and admin_boxes.ajax.php.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5960 — 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-2018-5960 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