CVE-2023-28474
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) in versions 9.0 through 9.1.3 is vulnerable to Stored XSS on Saved Presets on search.
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 confidenceConcrete CMS versions 9.0 through 9.1.3 contains a stored XSS vulnerability in the Saved Presets functionality of the search feature. Attackers can inject malicious JavaScript code into saved search presets, which executes when other users view or use those presets.
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 versionAccess the admin dashboard and navigate to Dashboard > System & Settings > Basics > Site Name, or check the file /application/config/app.php for the version stringAffected if Version is 9.0, 9.1.0, 9.1.1, 9.1.2, or 9.1.3 (any version below 9.2.0)
-
Locate the Saved Presets database tableQuery the database table CollectionSearchIndexAttributes (or search for tables containing 'search' and 'preset' in the name) to find saved search presetsAffected if The database contains records in any saved search preset table
-
Examine saved preset entries for script tagsRun a database query to find any preset entries containing HTML script tags, javascript: URIs, or event handler attributes (onclick, onload, etc.)Affected if Any saved preset record contains executable code such as <script> tags, event handlers, or javascript: protocols
Your environment is affected if you run Concrete CMS version 9.0 through 9.1.3 and have any saved search presets in your database that contain injected malicious script content.
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
Update Concrete CMS to version 9.1.4 or later. Apply output encoding and input validation to the saved presets feature as a defense-in-depth measure.
9.2.0 or later
- 1. Backup your Concrete CMS database and all files before proceeding
- 2. Download Concrete CMS version 9.2.0 or later from the official concretecms.com website
- 3. Review the official upgrade guide at concretecms.org/documentation/installation/upgrading_concrete
- 4. Upload the new files to your server, replacing the existing installation
- 5. Run the database upgrade script by accessing your site URL (the upgrade process will automatically trigger)
- 6. Clear any caching systems (application caches, CDN caches) after upgrade
- 7. Test the search functionality and saved presets to confirm the XSS vulnerability is remediated
- 8. Verify all other site functionality works as expected in a staging environment before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28474 — 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-28474 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