CVE-2025-46882
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 in victims' browsers when they view 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.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 Adobe Experience Manager versionAccess the AEM Welcome page or check the product version via the system console. Navigate to Help > About Adobe Experience Manager, or append /system/console/product to your AEM instance URL to view version details.Affected if The installed version is earlier than 6.5.23.0 or earlier than 2025.5.0, indicating the instance is within the affected version range.
-
Determine if AEM Forms module is enabledCheck whether AEM Forms or Adaptive Forms functionality is installed and active. Navigate to AEM Forms console at /aem/forms or verify the presence of form-related bundles in the OSGi console at /system/console/bundles.Affected if Forms functionality is enabled and accessible to users, making the XSS vector viable.
-
Verify low-privileged user access to form authoringReview user group permissions in AEM at /useradmin. Check if contributors or other low-privileged groups have access to create or edit Adaptive Forms, Form Data Model, or form submission endpoints.Affected if Low-privileged users can create or modify form content, allowing injection of malicious scripts.
-
Inspect form field configurations for input validationExamine Adaptive Form field components in the AEM Forms editor. Review the validation patterns and data format settings for text input fields at /editor.html/pages (or equivalent form authoring URLs).Affected if Form fields lack proper input validation or output encoding, which is the vulnerable configuration this CVE exploits.
-
Search for suspicious stored content in form submissionsQuery the AEM repository (via CRXDE or AEM Developer Tools) for known XSS patterns in form data. Check nodes under /content/forms and submission folders for script tags or javascript: URI schemes stored in field values.Affected if Malicious JavaScript payloads are present in stored form data, confirming active exploitation.
Your AEM instance is affected if it runs a version earlier than 6.5.23.0 or 2025.5.0, uses Forms functionality, and allows low-privileged users to inject unsanitized content into form fields.
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
Update Adobe Experience Manager to version 6.5.23 or later to obtain the vendor patch. Additionally, implement output encoding for form fields and consider Content Security Policy (CSP) headers to mitigate XSS risks.
Adobe Experience Manager 6.5.23.0 or later, or AEM Cloud Service 2025.5.0 or later
- Verify current Adobe Experience Manager version by checking the product about page or system console
- Review the Adobe Experience Manager 6.5.23.0 or 2025.5.0 release notes for upgrade requirements and breaking changes
- Ensure all custom code and third-party integrations are compatible with the target version
- Create a full backup of the AEM repository, database, and file system
- Test the upgrade in a non-production environment first
- Execute the upgrade following Adobe's official upgrade documentation for your deployment type (single server or cluster)
- Verify the upgrade was successful by checking the AEM version number
- Validate that all forms and user-generated content fields properly sanitize input to prevent XSS
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-46882 — 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-46882 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