CVE-2023-28477
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 · uneditedConcrete CMS (previously concrete5) versions 8.5.12 and below, and 9.0 through 9.1.3 is vulnerable to stored XSS on API Integrations via the name parameter.
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 confidenceStored cross-site scripting (XSS) vulnerability in Concrete CMS allows authenticated attackers to inject malicious JavaScript code via the name parameter in the API Integrations feature. The injected payload persists in the database and executes when other users view the API integrations page.
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< 9.2.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 Concrete CMS versionLocate the version file in the Concrete CMS installation directory, typically at /concrete/config/version.php or check the dashboard dashboard > system & settings > about > concrete cms for the version numberAffected if The installed version is below 9.2.0 (or 8.5.x versions below 8.5.13)
-
Verify API Integrations feature accessNavigate to the dashboard and check if you have access to the API Integrations section, usually found under System & Settings > API Integrations or Users > API Integrations. Only installations where authenticated users can access this feature are potentially affectedAffected if The API Integrations feature is accessible to authenticated users in the current installation
-
Examine database for API integration entriesQuery the database table that stores API integrations, typically something like 'ApiIntegrations' or 'OAuth2' related tables. Look for any entries in the 'name' field that contain unusual characters or patterns such as <script, javascript:, onerror, or encoded payloadsAffected if Any API integration entries exist with suspicious content in the name field that could indicate XSS payload injection
You are affected if your Concrete CMS version is below 9.2.0 AND the API Integrations feature is accessible to authenticated users who may have injected malicious scripts into the name parameter, which would now execute for other users viewing that page.
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 · scoped9.2.0
Upgrade Concrete CMS to version 9.1.4 or later (or 8.5.13+). Alternatively, implement input validation and output encoding on the name parameter in the API Integrations functionality.
Concrete CMS 9.2.0
- Backup your Concrete CMS database and files before upgrading
- Ensure you have a complete backup of your current installation
- Test the upgrade in a staging environment before applying to production
- Upgrade Concrete CMS to version 9.2.0 or later
- Verify the upgrade was successful by logging into the admin dashboard
- Confirm the XSS vulnerability is remediated by testing the API Integrations name parameter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28477 — 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-2023-28477 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