CVE-2024-26051
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 · uneditedAdobe Experience Manager versions 6.5.19 and earlier 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 · moderate confidenceAdobe Experience Manager versions 6.5.19 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious JavaScript into form fields, which persists in the system and executes when legitimate users browse to pages containing the compromised fields.
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.20.0< 2024.3.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify installed AEM versionLog in to AEM as administrator and navigate to Help > About Adobe Experience Manager, or access the System Information console at /system/console/info to retrieve the product versionAffected if The displayed version is below 6.5.20.0 or below 2024.3.0
-
Confirm AEM edition and deployment typeVerify this is a standard AEM Forms or AEM Sites deployment rather than a minimal installation without form componentsAffected if Standard AEM installation with form authoring capabilities is present
-
Locate form components that accept user inputReview the AEM content structure in CRX/DE (accessible at /crx/de) or use the Template Editor to identify form fields, text inputs, or data-capable components that store user submissionsAffected if Form components storing user data in the repository exist in the implementation
-
Verify input validation exists on form fieldsExamine the form component configurations and their validation rules in the AEM Forms or Adaptive Forms settings, checking for server-side validation rules on each fieldAffected if Form fields lack server-side input validation or allow unrestricted text entry without sanitization rules
-
Check output encoding on rendered form fieldsInspect the HTL or JSP templates rendering the form fields (typically in /apps or /libs) to confirm context-aware output encoding is applied when displaying stored form dataAffected if Templates render stored form values without proper context-aware encoding (e.g., no use of encoding utilities or safe HTML filters)
Your AEM instance is affected if it runs version 6.5.20.0 or earlier, or 2024.3.0 or earlier, and contains form fields that accept user input without proper input validation and output 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 · scoped6.5.20.02024.3.0
Update Adobe Experience Manager to a patched version. Implement input validation and output encoding on form fields to prevent script injection.
Adobe Experience Manager 6.5.20.0+ (on-premise) or AEM Cloud Service 2024.3.0+
- Identify your AEM deployment type (on-premise 6.5.x or AEM as a Cloud Service)
- For on-premise AEM 6.5.x deployments: Upgrade to AEM 6.5.20.0 or later
- For AEM as a Cloud Service: Ensure version is 2024.3.0 or later
- Review Adobe's official upgrade documentation for your deployment type
- Test the upgrade in a non-production environment before deploying to production
- Schedule a maintenance window for the upgrade process
- Perform the upgrade following Adobe's documented procedures
- Validate the fix by confirming the stored XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26051 — 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-2024-26051 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