CVE-2018-18200
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 · uneditedThere is a SQL injection in Benutzerverwaltung in REDAXO before 5.6.4.
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 confidenceA SQL injection vulnerability exists in the Benutzerverwaltung (user management) module of REDAXO CMS versions prior to 5.6.4. Attackers can exploit unsanitized user input in the user management functionality to inject malicious SQL statements, potentially allowing unauthorized access to sensitive data, data exfiltration, or database manipulation.
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< 5.6.4CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Locate the REDAXO CMS version fileAccess the REDAXO installation directory and look for a version indicator file (such as redaxo/include/master.inc.php, composer.json, or a VERSION file in the root directory). Open the file and locate the version number.Affected if The version number found is less than 5.6.4 (for example, 5.6.0, 5.5.x, or earlier)
-
Verify version via admin backendLog in to the REDAXO admin/backend area. Navigate to the system information or settings page where the installed version is displayed.Affected if The displayed version is < 5.6.4
-
Confirm user management module is presentCheck that the Benutzerverwaltung (user management) module is installed and accessible in the REDAXO backend. This is typically found under the settings or system menu in the admin area.Affected if The user management module exists and the installed REDAXO version is < 5.6.4
A system is affected by CVE-2018-18200 if the installed REDAXO CMS version is anything earlier than 5.6.4 and the Benutzerverwaltung user management module is present and accessible.
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.
dbcve · scoped5.6.4
Upgrade to REDAXO version 5.6.4 or later which contains the fix for this SQL injection vulnerability in the user management module.
REDAXO 5.6.4
- Upgrade REDAXO to version 5.6.4 or later to resolve the SQL injection vulnerability in the Benutzerverwaltung (user management) module
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2018-18200 — 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-18200 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