Reflected Cross-site Scripting (XSS) in ACS CommonsGHSA-7r83-w6r8-fh6w
MEDIUMFix: Adobe-Consulting-Services/acs-aem-commons@14d769cGHSA-7r83-w6r8-fh6w is a medium-severity (CVSS 6.1) 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.
EPSS Exploitation Probability
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
com.adobe.acs:acs-aem-commonsReal-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
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.adobe.acs:acs-aem-commons | all versions | 4.10.0com.adobe.acs:acs-aem-commons:4.10.0 |
Affected Products
acrobatadobeacrobat dcadobeacrobat readeradobeacrobat reader dcadobeDetection & mitigation playbook
Open-source dependencyDetect
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-7r83-w6r8-fh6w 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
Is GHSA-7r83-w6r8-fh6w in your dependencies?
Find it across Maven, including transitive dependencies.