CVE-2025-47033
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-privileged attacker can inject malicious JavaScript payloads into vulnerable form input fields. When authenticated users browse to pages containing these compromised fields, the malicious script executes in their browsers, potentially allowing session hijacking or unauthorized actions.
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.
-
Check installed Adobe Experience Manager versionNavigate to the AEM Welcome page (http://hostname:port/aem/start.html) and locate the version information, or check the version.properties file in the crx-quickstart folderAffected if The version is lower than 6.5.23.0 or lower than 2025.5.0
-
Identify form field usage in AEMReview your AEM instance for any form components, adaptive forms, or custom form implementations that accept user inputAffected if Form fields that accept user input are present and accessible to low-privileged users
-
Verify low-privileged user access to formsCheck user group permissions for contributors or content authors who have access to create or edit form contentAffected if Users with low privileges (contributor, author, or similar roles) can create or modify form field values
-
Inspect form field configuration for input validationExamine the form field component configurations in AEM for any HTML encoding or input validation settings applied to user-supplied valuesAffected if Form fields lack output encoding or input validation on submitted values
-
Review recent form submissions for suspicious contentCheck the content repository (under /content or relevant form submission paths) for any JavaScript tags, script elements, or event handler attributes in form field dataAffected if Malicious JavaScript payloads are found stored in form field content
Your environment is affected if the installed AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privileged users can access or edit form input fields without proper 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.23.02025.5.0
Upgrade Adobe Experience Manager to a version newer than 6.5.22 as provided in the vendor advisory. Additionally, implement output encoding on form fields and consider Content Security Policy (CSP) headers to mitigate XSS execution.
Adobe Experience Manager 6.5.23.0 or later (6.5.x line) or 2025.5.0 or later
- Obtain Adobe Experience Manager 6.5.23.0 (or later 6.5.x) from Adobe Software Distribution or your licensing portal
- Alternatively, obtain Adobe Experience Manager 2025.5.0 (or later) for the newer release line
- Review the Adobe release notes and installation instructions specific to the version being applied
- Create a full backup of the AEM instance including repository, configuration, and custom code
- Stop the AEM instance before applying the update
- Install the new version following Adobe's standard upgrade procedure
- Verify the installation completed successfully
- Test that the affected form fields no longer accept malicious script injection
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47033 — 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-47033 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