Sling CmsApplication · Apache
CVE-2022-46769
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 improper neutralization of input during web page generation ('Cross-site Scripting') [CWE-79] vulnerability in Sling App CMS version 1.1.2 and prior may allow an authenticated remote attacker to perform a reflected cross-site scripting (XSS) attack in the site group feature. Upgrade to Apache Sling App CMS >= 1.1.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 · high confidenceA reflected cross-site scripting (XSS) vulnerability in Apache Sling App CMS versions 1.1.2 and prior allows authenticated attackers to inject malicious scripts through the site group feature. The vulnerability stems from improper input neutralization during web page generation, enabling script execution in victim browsers.
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
Sling CmsApplication
< 1.1.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
- 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 the installed Apache Sling App CMS versionAccess the CMS admin interface and navigate to the system information or about section, or check the version in the deployed WAR/bundle files. Alternatively, query the Sling CMS API endpoint that exposes version information if available.Affected if The installed version is 1.1.2 or any version prior to 1.1.4.
-
Verify access to the site group featureLog in to the CMS with an authenticated account and navigate to the site group management interface, typically found under the CMS administration or user management sections.Affected if The site group feature is accessible and functional in the CMS.
-
Check if authenticated user access is availableConfirm you have a valid CMS user account with permissions to access the site group feature. The vulnerability requires an authenticated attacker.Affected if You can authenticate to the CMS and access features that accept user input for site group configuration.
-
Inspect the site group input fields for lack of output encodingUsing an authenticated session, submit test input containing HTML or script tags (such as <script>alert(1)</script>) into the site group name or description fields, then view the rendered page where this data is displayed.Affected if The submitted script tags are rendered as literal text in the browser without encoding, indicating the vulnerability is present.
You are affected if your Apache Sling App CMS version is 1.1.2 or prior (below 1.1.4) AND you have the site group feature 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.
dbcve · scoped1.1.4
Upgrade Apache Sling App CMS to version 1.1.4 or later. If upgrading is not immediately feasible, implement input validation and output encoding on the site group feature as a compensating control.
1.1.4
- Verify current Sling CMS version by checking the installed package or admin interface
- Review upgrade documentation at the official Apache Sling website (sling.apache.org) for version-specific upgrade instructions
- Create a complete backup of the current CMS instance including database and configuration files
- Test the upgrade in a non-production environment before deploying to production
- Upgrade to Apache Sling App CMS version 1.1.4 or later
- Verify the upgrade was successful and the XSS vulnerability is resolved by testing the site group feature
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Sling Cms
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46769 — 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-46769 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