How severe is CVE-2022-28820?

CVE-2022-28820 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-28820?

CVE-2022-28820 affects the following packages: com.adobe.acs:acs-aem-commons (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-28820?

Update com.adobe.acs:acs-aem-commons to 5.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-28820 is resolved across your whole dependency graph.

How do I detect CVE-2022-28820 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.adobe.acs:acs-aem-commons, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-28820 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2022-28820 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-28820 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-28820?

CVE-2022-28820 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-28820?

CVE-2022-28820 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-28820 published, and has it been updated?

CVE-2022-28820 was published on April 21, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2022-28820 — acs-aem-commons

MEDIUM

CVE-2022-28820 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in com.adobe.acs:acs-aem-commons. A fix is available for com.adobe.acs:acs-aem-commons — see the affected versions and patch details below.

Adobe Consulting Services Reflected Cross-Site Scripting Arbitrary Code Execution

Also known asGHSA-w5m2-299g-rff5

Published

Apr 21, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕com.adobe.acs:acs-aem-commons

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

ACS 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 sanitized.

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.

Patches

This issue has been resolved in 5.2.0.

Workarounds

None

References

N/A

For more information

If you have any questions or comments about this advisory open an issue in acs-aem-commons.

Credit

This issue was discovered and reported by Black Lantern Security.

https://hackerone.com/reports/1466020

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.adobe.acs:acs-aem-commons`	all versions	5.2.0`com.adobe.acs:acs-aem-commons:5.2.0`

Affected Products

1 product · 1 configurations

Application

acs aem commonsadobe

< 5.2.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.adobe.acs:acs-aem-commons, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.adobe.acs:acs-aem-commons to 5.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-28820 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact ACS 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 sanitized. 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

O3 Security · Impact-Aware SCA

Is CVE-2022-28820 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

acs-aem-commons

4.9/10

Code-Review5/10

Maintained10/10

Branch-ProtectionN/A

Assessed Nov 2, 2026

Timeline

Disclosed

Apr 21, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-28820

GHSA-w5m2-299g-rff5

References

Advisorygithub.com · GHSA w5m2 299g rff5 Advisorygithub.com · CVE 2022 28820.json Advisorynvd.nist.gov · CVE 2022 28820 Packagegithub.com · acs aem commons

Related vulnerabilities

Also affects acs-aem-commons

This CVE is medium severity; 2 of 2 other CVEs affecting acs-aem-commons are rated as high or higher (top: high).

CVE-2021-21043CVE-2021-21028

Same weakness: CWE-79

This CVE is medium severity; 6 of 6 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-88986CVE-2026-63197CVE-2026-55649CVE-2026-113787CVE-2026-44267CVE-2026-96632Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-28820 — acs-aem-commons

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

Workarounds

References

For more information

Credit

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-28820 in your dependencies?