CVE-2025-47076
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.22 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low privileged 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 versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privilege attacker can inject malicious JavaScript into form inputs that persists on the page, executing in the browsers of users who view the affected content.
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.23.0< 2025.5.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 versionAccess the AEM Web Console at /system/console or check the welcome page footer for the version number. Alternatively, check the crx-quickstart/license.properties file for the version string.Affected if The installed version is 6.5.22 or earlier, or any version below 2025.5.0 (for cloud/as-a-service variants) and is less than 6.5.23.0 (for on-premise).
-
Locate form field implementations in AEMReview the AEM content structure for pages containing Adaptive Forms, Core Form Components, or custom form implementations. Check /apps or /content for form containers and their input fields.Affected if Form components that accept user input exist in the AEM instance and are accessible to low-privilege users.
-
Inspect HTML output of form fields for encodingSubmit test input containing special characters (e.g., <script>alert(1)</script>) into a form field, then view the page source or inspect the element in a browser to see if the input is properly HTML-encoded.Affected if The form field output shows raw unencoded characters (e.g., <script> appears as <script> in the page source rather than <script>).
-
Verify input validation is configuredCheck the form component's validation settings in the AEM Editor or through the Rule Editor for Adaptive Forms. Look for any Input Validation patterns or constraints defined on text fields.Affected if Form fields lack input validation rules or pattern constraints, allowing special characters to be submitted and stored.
-
Check for persisted malicious content in form dataQuery the AEM repository (via CRXDE or the Query tool) for form submission nodes in /content/forms/af or custom form paths. Inspect stored values for unsanitized script tags or event handlers.Affected if Stored form submission data contains unsanitized HTML or JavaScript that would execute when rendered.
If the AEM version is below 6.5.23.0 (or below 2025.5.0 for cloud) AND custom or Adaptive Forms are in use with unencoded form field output, the environment is vulnerable to stored XSS.
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.23.02025.5.0
Upgrade to AEM 6.5.23 or later to obtain the vendor patch. Until upgraded, implement output encoding and input validation on form fields as a compensating control.
AEM 6.5.23.0 or AEM 2025.5.0 (whichever branch is applicable to your deployment)
- 1. Review Adobe Experience Manager release notes for versions 6.5.23.0 and 2025.5.0 to understand changes and fixes included
- 2. Back up your current AEM instance including repository, database, and configurations
- 3. Test the upgrade in a non-production environment before deploying to production
- 4. Ensure custom code and third-party integrations are compatible with the target version
- 5. Follow Adobe's official upgrade documentation for your specific AEM deployment type (on-premise or cloud)
- 6. After upgrading, verify that the stored XSS vulnerability is resolved by testing the affected form fields
- 7. Deploy the upgraded version to production after successful validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47076 — 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-2025-47076 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