CVE-2020-24445
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 · uneditedAEM's Cloud Service offering, as well as version 6.5.6.0 (and below), are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by an attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.
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 confidenceAdobe Experience Manager contains a stored XSS vulnerability in form fields affecting Cloud Service and versions 6.5.6.0 and below. Attackers can inject malicious JavaScript into form field inputs that persists on the server and executes when users view the affected pages.
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<= 6.5.6.0all versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
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.
-
Determine AEM versionAccess the AEM Welcome page or check the product.info via the system console (system/console/systeminfo). Locate the 'Adobe Experience Manager' version entry.Affected if Version listed is 6.5.6.0 or lower, or the deployment is AEM Cloud Service (any version)
-
Identify form field componentsReview the AEM Forms implementation and custom form components in the /apps directory. Identify all form fields that accept user input, particularly in content fragments, adaptive forms, or custom components.Affected if Form fields accepting user-supplied input exist in the environment without documented sanitization
-
Verify output encoding on form inputsInspect the JSP, HTL, or Sightly templates that render form field values. Check if server-side output encoding (such as escaping HTML entities) is applied before displaying submitted form data.Affected if Form input values are rendered without HTML encoding or sanitization functions
-
Test for stored XSS injectionSubmit a benign test payload like <script>alert('XSS')</script> into accessible form fields, then navigate to a page that displays the submitted data to observe if the script executes.Affected if The submitted script tag renders as executable code rather than being escaped or stripped
You are affected if running AEM Cloud Service of any version, or AEM version 6.5.6.0 or below, AND form fields exist that render user input without proper HTML encoding.
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 · scopedApply the appropriate Adobe security patch for AEM and implement output encoding/HTML sanitization on all user-supplied form inputs to prevent script execution.
AEM 6.5.7.0 (January 2021 security update) or later; AEM Cloud Service (latest managed version)
- Confirm current AEM version by navigating to /system/console/bundles or checking the About Adobe Experience Manager page
- For AEM 6.5.6.0 and below: Schedule a maintenance window for the upgrade
- Back up all AEM content, repository (Oak repository), and configuration files before proceeding
- Download AEM 6.5.7.0 or later from the Adobe Software Distribution portal (software.adobe.com)
- Stop the current AEM instance
- Run the upgrade installer following Adobe's upgrade documentation for your current version
- After upgrade, verify all custom applications and workflows function correctly
- For AEM Cloud Service: Contact Adobe support to confirm the latest patch has been applied to your environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24445 — 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-2020-24445 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