CVE-2025-47079
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-privilege attacker can inject malicious JavaScript payloads into these fields, which persist in the system. When authenticated users with higher privileges browse to pages containing the compromised form 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.
-
Identify the installed AEM versionAccess the AEM Web Console (typically at /system/console/config) or check the manifest file in the installation directory. The version is also visible on the Welcome page under 'Version Information' or via the 'version' command in the OSGi console.Affected if The installed version is 6.5.22 or earlier, or any version prior to 2025.5.0 for the monthly release track (versions earlier than 6.5.23.0).
-
Review form field configurations for user inputNavigate to the Forms section in AEM (typically /aem/forms.html or /libs/foundation/components/form) and identify any form components that accept user-submitted content. Check the component XML definitions under /apps or /libs for form field components.Affected if Form components that accept user input exist in the environment and do not have explicit output encoding configured.
-
Inspect stored form data for suspicious contentQuery the AEM repository (via CRXDE Lite at /crx/de or using the Query Manager) for form submission data. Look in nodes under /content/usergenerated or custom form submission paths. Search for patterns like <script>, javascript:, onerror=, onload=, or other HTML event handlers.Affected if Any form submission nodes contain unsanitized HTML or JavaScript code, particularly script tags or event handler attributes.
-
Verify output encoding on form field rendersExamine the JSP, HTL (Sightly), or HTML template files responsible for rendering form field values in your application (typically under /apps/your-project/components). Check if server-side encoding functions such as xssAPI.encodeForHTML() or equivalent context-aware escaping are applied to user-supplied form values before output.Affected if Form field output templates do not apply server-side output encoding to user-submitted values.
-
Assess user permission models for form creationReview the AEM user and group permissions in the User Administration console (/security/users.html). Determine if low-privilege users (contributors, content authors without admin rights) have permission to create or edit form components.Affected if Low-privilege users have write access to form components or form submission content, allowing them to inject malicious payloads.
You are affected if your AEM version is earlier than 6.5.23.0 or earlier than 2025.5.0 AND your forms accept user input without proper server-side output encoding, allowing stored XSS payloads to persist and execute for higher-privilege users.
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 per Adobe's official security advisory. Additionally, implement output encoding on form field outputs and consider Content Security Policy (CSP) headers as defense-in-depth until the patch is applied.
AEM 6.5.23.0 or later (or AEM as a Cloud Service 2025.5.0 or later)
- Backup the current AEM instance including repository, database, and configuration files
- Download Adobe Experience Manager 6.5.23.0 or later (or 2025.5.0+ for the 2024 release line) from the official Adobe Distribution Center
- Test the upgrade in a non-production/staging environment first
- Stop the AEM instance and any related services
- Run the upgrade installer following Adobe's documented upgrade procedure: https://helpx.adobe.com/experience-manager/6-5/release-notes/sp-release-notes.html
- After upgrade completes, clear the AEM cache and repository index
- Start the AEM instance and verify all custom applications function correctly
- Verify the XSS vulnerability is remediated by testing the previously affected form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47079 — 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-47079 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