CVE-2022-28820
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 · uneditedACS Commons version 5.1.x (and earlier) suffers from a Reflected Cross-site Scripting (XSS) vulnerability in /apps/acs-commons/content/page-compare.html endpoint via the a and b GET parameters. User input submitted via these parameters is not validated or sanitised. An attacker must provide a link to someone with access to AEM Author, and could potentially exploit this vulnerability to inject malicious JavaScript content into vulnerable form fields and execute it within the context of the victim's browser. The exploitation of this issue requires user interaction in order to be successful.
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 confidenceReflected XSS vulnerability in ACS Commons version 5.1.x and earlier. The /apps/acs-commons/content/page-compare.html endpoint does not validate or sanitize the 'a' and 'b' GET parameters, allowing injection of malicious JavaScript that executes within the context of a victim's browser when they access a crafted link.
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< 5.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify ACS Commons bundle is installedNavigate to AEM Felix Console at /system/console/bundles and search for 'acs-commons' bundle, or check for package installation at /crx/packmgrAffected if The ACS Commons bundle or package is present in the AEM instance
-
Determine installed ACS Commons versionIn Felix Console bundle view, locate the acs-commons bundle and read the Version column, or check the package version in /crx/packmgrAffected if The installed version is 5.1.x or any version earlier than 5.2.0
-
Confirm page-compare.html endpoint existsAttempt to access the URL pattern /apps/acs-commons/content/page-compare.html in the AEM instance (may require authentication)Affected if The endpoint returns a valid response rather than a 404 error
-
Check if vulnerable parameters accept unsanitized inputWith the bundle version confirmed as < 5.2.0, submit a test request to page-compare.html with a benign script tag in parameters 'a' or 'b' (e.g., ?a=<script>alert(1)</script>) and verify if the value is reflected unescaped in the responseAffected if The parameter value is reflected in the HTML response without encoding or sanitization
A user is affected if ACS Commons version 5.1.x or earlier is installed and the /apps/acs-commons/content/page-compare.html endpoint reflects unsanitized 'a' or 'b' parameters in its response.
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 · scoped5.2.0
Upgrade ACS Commons to version 5.2.0 or later to remediate this vulnerability.
ACS AEM Commons 5.2.0
- Identify the current version of ACS AEM Commons installed in the AEM instance by checking the OSGi console or the content package version
- Download ACS AEM Commons version 5.2.0 or later from the official Adobe GitHub repository or Maven Central
- Deploy the new ACS AEM Commons content package to the AEM instance using Package Manager or CRX/DE
- Verify the package installed successfully and the bundle is in active state
- Test the /apps/acs-commons/content/page-compare.html endpoint to confirm the fix is applied (the a and b parameters should now be properly sanitized)
- Clear the AEM instance cache and rebuild any index if necessary
Generated from the published advisory — verify against the referenced sources before acting.
- 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-28820 — 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-28820 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