CVE-2025-46924
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 into vulnerable form inputs, which persists in the system and executes when other users view pages containing those 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.
-
Confirm AEM is runningCheck if Adobe Experience Manager is accessible on the typical author (port 4502) or publish (port 4503) ports, or look for java processes running cq-author or cq-publishAffected if AEM instance is accessible on the network
-
Identify the installed AEM versionAccess the AEM System Information console at /system/console/status-SystemInfo or check the version.properties file in the crx-quickstart directoryAffected if The version displayed is 6.5.22 or earlier, or falls below 6.5.23.0 or 2025.5.0
-
Verify if forms using AEM form components are in useReview the AEM instance for pages containing Form components (either Foundation Form components or Core Components Form), which are typically created using the Editable Templates or dynamic media implementationsAffected if Form components that accept user input are present and actively used on the AEM instance
-
Check if user-supplied form field data is rendered without encodingSubmit test input containing script-safe characters (such as <script>alert(1)</script>) into a form field on a published page, then view the submitted data as another user would see it in the AEM inbox or form submissionsAffected if The submitted test script content renders as executable HTML rather than being encoded or stripped
You are affected if your AEM version is below 6.5.23.0 or 2025.5.0 AND you have form fields that accept and display user-submitted content 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
Implement proper input validation and output encoding on AEM form fields, or apply available Adobe security patches for AEM 6.5.22 and later.
AEM 6.5.23.0 or later; AEM as a Cloud Service 2025.5.0 or later
- 1. Verify current AEM version by checking the Adobe Experience Manager Web Console (Go to /system/console/config or check the 'About Adobe Experience Manager' section in the navigation)
- 2. Create a full backup of the AEM instance including the repository (crx-quickstart), database, and any custom code/configurations
- 3. If using AEM 6.5.x: Download AEM 6.5.23.0 or later from the Adobe Software Distribution portal
- 4. If using AEM as a Cloud Service: Ensure the environment is updated to release 2025.5.0 or later through Cloud Manager
- 5. Test the upgrade in a staging environment that mirrors production before deploying to production
- 6. Deploy the upgrade during a planned maintenance window following standard AEM upgrade procedures
- 7. Verify the upgrade was successful by checking the AEM version after startup
- 8. Test the specific form fields that were vulnerable to ensure the XSS vulnerability is remediated
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-46924 — 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-46924 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