How severe is GHSA-f92j-qf46-p6vm?

No CVSS score has been assigned to GHSA-f92j-qf46-p6vm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f92j-qf46-p6vm?

GHSA-f92j-qf46-p6vm affects the following packages: com.adobe.acs:acs-aem-commons (Maven). Ecosystems affected: Maven.

How do I fix GHSA-f92j-qf46-p6vm?

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

How do I detect GHSA-f92j-qf46-p6vm 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 GHSA-f92j-qf46-p6vm if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-f92j-qf46-p6vm actively exploited in the wild?

No public exploit code has been indexed for GHSA-f92j-qf46-p6vm 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 GHSA-f92j-qf46-p6vm?

GHSA-f92j-qf46-p6vm has an EPSS (Exploit Prediction Scoring System) score of 4.3%, placing it in the 91th 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 GHSA-f92j-qf46-p6vm?

GHSA-f92j-qf46-p6vm is classified as Use After Free (CWE-416). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f92j-qf46-p6vm published, and has it been updated?

GHSA-f92j-qf46-p6vm was published on February 2, 2021 and was last updated on July 8, 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

Reflected Cross-site Scripting in ACS CommonsGHSA-f92j-qf46-p6vm

Fix: Adobe-Consulting-Services/acs-aem-commons@14d769c

GHSA-f92j-qf46-p6vm is a Use After Free 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.

Also known asCVE-2021-21028 CVE-2021-21043 GHSA-7r83-w6r8-fh6w

Published

Feb 2, 2021

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.3%probability of exploitation in next 30 days

Lower Risk+0.18%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

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

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 4.9.2 (and earlier) suffers from a Reflected Cross-site Scripting (XSS) vulnerability in version-compare and page-compare due to invalid JCR characters that are not handled correctly.

An attacker 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. Exploitation of this issue requires user interaction in order to be successful.

Patches

This issue has been resolved in v4.10.0

Workarounds

No workaround exist.

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 Christopher Whipp ([email protected]).

Affected Packages

1 total 1 fixed

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

Affected Products

4 products · 6 configurations

Application

acrobatadobe

≥ 20.0 && ≤ 20.001.30018

range

Application

acrobat dcadobe

≤ 20.013.20074

range

Application

acrobat readeradobe

≥ 20.0 && ≤ 20.001.300183

range

Application

acrobat reader dcadobe

≤ 20.013.20074

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 4.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f92j-qf46-p6vm is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

### Impact ACS Commons version 4.9.2 (and earlier) suffers from a Reflected Cross-site Scripting (XSS) vulnerability in version-compare and page-compare due to invalid JCR characters that are not handled correctly. An attacker 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. Exploitation of this issue requires user interaction in order to be successful. ### Patches This issue has been resolved in v4.10.0 ### Workarounds No workaround exist. ### References N/A ### F