CVE-2025-46844
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The malicious payload is stored in the system and executes when other users view pages containing the affected form 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.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.
-
Verify Adobe Experience Manager versionAccess the AEM Web Console at /system/console/bundles or check the version.properties file in the crx-quickstart directory. You can also navigate to Help > About Adobe Experience Manager in the AEM console to see the exact version number.Affected if The installed version is less than 6.5.23.0 or less than 2025.5.0
-
Identify form components in useSearch the AEM content repository (via CRXDE Lite at /crx/de or using Query Builder) for nodes of type cq:Component that represent form fields, such as core/wcm/components/form/text/v2/text or foundation/components/form/text. Check the content structure under /content for pages containing these form components.Affected if Form components that accept user input are present in the content tree and accessible to low-privileged users
-
Inspect form field configurations for input validationReview the Edit dialog configuration of form components in CRXDE Lite under /apps or /libs. Examine the validation node (granite:data) attached to form input fields to determine if server-side validation rules are defined.Affected if Form fields lack input validation rules or the validation is insufficient to prevent script injection
-
Search for suspicious script payloads in content repositoryUse AEM Query Builder or CRXDE Lite search to query the /content nodes for common XSS patterns in form field values, such as <script, javascript:, onerror=, onload=, and similar event handler attributes stored in text fields.Affected if Any form field values in the repository contain encoded or raw JavaScript code that could execute in a user browser
Your environment is affected if the installed AEM version is below 6.5.23.0 or below 2025.5.0 AND forms accepting user input are present in your content, regardless of whether malicious payloads are currently detected.
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. Additionally, implement input validation and output encoding on all form fields to prevent XSS injection.
6.5.23.0 (for 6.5.x line) or 2025.5.0 (for 2025.x line)
- 1. Identify the current Adobe Experience Manager version by checking the product about page or system console
- 2. For 6.5.x line users: Plan upgrade to version 6.5.23.0 or later
- 3. For 2025.x line users: Plan upgrade to version 2025.5.0 or later
- 4. Perform a full backup of the AEM instance including repository, database, and configurations
- 5. Test the upgrade in a staging environment before applying to production
- 6. Apply the upgrade following Adobe's standard upgrade documentation
- 7. Verify the upgrade was successful and the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46844 — 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-46844 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