CVE-2022-28803
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 · uneditedIn SilverStripe Framework through 2022-04-07, Stored XSS can occur in javascript link tags added via XMLHttpRequest (XHR).
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 stored Cross-Site Scripting (XSS) vulnerability exists in SilverStripe Framework through April 2022, allowing attackers to inject malicious JavaScript via javascript link tags that are added through XMLHttpRequest (XHR) calls. The malicious script is persisted on the server and executes when other users view the affected content.
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< 4.10.9CVSS 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 SilverStripe framework versionLocate the version file or check composer.json in your SilverStripe installation root directory for the 'silverstripe/framework' package versionAffected if The installed version is below 4.10.9 (e.g., 4.10.0 through 4.10.8, or any 4.x version prior to 4.10.9)
-
Confirm XHR content submission is enabledReview your application configuration to determine if XMLHttpRequest-based content submission is permitted for user-generated content or link fieldsAffected if XHR-based content submission is enabled and accessible to untrusted users
-
Inspect stored content for javascript: linksQuery your database for records containing 'javascript:' protocol links in text fields that accept link input, particularly content submitted via XHRAffected if Any records contain javascript: link tags that were added through XHR calls and are rendered without proper encoding
You are affected if your SilverStripe framework version is below 4.10.9 AND your application accepts XHR-submitted content that can contain javascript: links, as the malicious script would be stored and executed when other users view the 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 · scoped4.10.9
Implement proper input validation and output encoding for javascript link tags in XHR requests. The fix should sanitize any user-supplied content before storage and apply context-appropriate encoding when rendering the content.
SilverStripe Framework 4.10.9 or later
- Backup your database and entire SilverStripe project directory before proceeding
- Update your composer.json to require silverstripe/framework:^4.10.9
- Run 'composer update silverstripe/framework' to install the fixed version
- Clear the SilverStripe cache by deleting the cache directory (usually silverstripe-cache or tmp/silverstripe-cache)
- Run /dev/build?flush=all to rebuild the database schema
- Test your application to ensure functionality remains intact
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-2022-28803 — 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-2022-28803 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