CVE-2025-47052
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 where a low-privileged authenticated attacker can inject malicious JavaScript into form fields. When victims browse to pages containing these compromised fields, the injected script executes in their browsers.
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 your Adobe Experience Manager versionAccess the AEM system information page at /system/console/status-productinfo or check the crx-quickstart folder for the version file. You can also run: curl -s http://localhost:4502/libs/granite/core/content/login.html (version info is typically in the startup logs or AEM Quickstart properties)Affected if The installed version is lower than 6.5.23.0 or lower than 2025.5.0 (the 2024.x and earlier releases)
-
Identify form field configurations in AEMReview your AEM instance for Adaptive Forms, Core Components form fields, or custom form implementations. Check content fragments and experience fragments that may contain user-editable form fields. Access the CRX/DE console at /crx/de/index.jsp and navigate to /content or /apps to locate form componentsAffected if Your AEM instance contains editable form fields that accept user input without proper validation configured
-
Verify input validation on form fieldsExamine the validation settings for form components in AEM. Check the validation pattern and rules configured for text input fields, email fields, and other form elements. In CRX/DE, inspect the xml behind form components for input validation rulesAffected if Form fields lack input validation constraints or allow HTML/script content in their validation patterns
-
Check for existing malicious scripts in stored contentSearch the AEM content repository (via CRX/DE query tool or Groovy console) for common XSS patterns in form field data. Look for patterns like <script, javascript:, onload=, onerror=, or other HTML event handlers stored in text fieldsAffected if Any stored form content contains encoded or raw JavaScript tags, event handlers, or suspicious encoded payloads
Your environment is affected if the AEM version is below 6.5.23.0 or below 2025.5.0 AND your forms accept user input without proper input validation and output encoding protections.
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 version 6.5.23 or later, or implement input validation and output encoding on affected form fields to prevent script injection.
AEM 6.5.23.0 or AEM 2025.5.0 (or later)
- Identify your current Adobe Experience Manager version by checking the product welcome page or system console
- Review the Adobe Experience Manager 6.5.23.0 or 2025.5.0 release notes for new features, deprecated functionality, and known issues
- Ensure your current environment meets the prerequisites for upgrading to the target version (6.5.23.0 or 2025.5.0)
- Backup your current AEM instance including the repository, database, and configurations
- Test the upgrade in a non-production environment to verify compatibility with custom code, third-party integrations, and workflows
- Perform the upgrade following Adobe's official upgrade documentation for your deployment type (standalone or cluster)
- After upgrade, verify that all form fields and user-generated content properly encode output to prevent XSS
- Validate that the stored XSS vulnerability is no longer exploitable by testing malicious script injection in vulnerable form fields
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-47052 — 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-47052 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