CVE-2021-28053
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 · uneditedAn issue was discovered in Centreon-Web in Centreon Platform 20.10.0. A SQL injection vulnerability in "Configuration > Users > Contacts / Users" allows remote authenticated users to execute arbitrary SQL commands via the Additional Information parameters.
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 Centreon-Web's 'Configuration > Users > Contacts / Users' page allows remote authenticated attackers to execute arbitrary SQL commands through the Additional Information parameters.
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= 20.10.0CVSS 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 Centreon installation and versionLocate the Centreon installation directory and check the version file, typically in /usr/share/centreon or the web root. Look for a version.php, VERSION, or similar file that displays the Centreon version number.Affected if The installed Centreon version is exactly 20.10.0
-
Verify Centreon-Web component versionCheck the Centreon-Web package or module version through the web interface footer, or by examining the centreon-web package version via the system package manager (dpkg, rpm) if installed via packages.Affected if The Centreon-Web component version matches 20.10.0
-
Confirm web interface accessibilityAttempt to access the Centreon web login page to confirm the web interface is exposed and operational.Affected if The Centreon web interface is accessible and accepts authentication
-
Check for Contacts/Users configuration accessLog into Centreon and navigate to Configuration > Users > Contacts / Users to confirm this menu path exists and is accessible.Affected if The Configuration > Users > Contacts / Users page is accessible to the authenticated user
-
Identify Additional Information fieldsWithin the Contacts/Users configuration page, locate any 'Additional Information' or similar free-text fields associated with user contact definitions.Affected if Additional Information fields are present in the user contact configuration and accept user input
You are affected if Centreon version is exactly 20.10.0 and the web interface with Configuration > Users > Contacts / Users and Additional Information fields is accessible to authenticated users.
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 vendor patch (Centreon 20.10.10+) or upgrade to a supported version; implement parameterized queries or robust input validation on the Additional Information fields.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28053 — 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-2021-28053 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