CVE-2025-49547
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 FP11.4 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. Scope is changed.
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 · moderate confidenceAdobe Experience Manager versions FP11.4 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 executes when other users view pages containing those fields. The CVSS scope change indicates the vulnerability impacts components beyond 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.22.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 AEM versionAccess the AEM system console at /system/console/about.json or check the version displayed in the AEM welcome screen under 'Product Information'. Compare the version number to the affected range (6.5.22.0 and earlier).Affected if The installed AEM version is 6.5.22.0 or any earlier 6.5.x version.
-
Enumerate form components in useReview the AEM content structure under /content for pages containing Adaptive Form components or custom form fields. Use the AEM search functionality to locate components of type 'core/fb/components/form' or similar form container components.Affected if Adaptive Forms or custom form components are present in the AEM content.
-
Inspect form field template configurationsNavigate to /apps and review the HTL/Sightly templates for form components (typically under /libs/fb/components or /apps/*/components/form). Check the .html template files for each form input type to verify output encoding is applied using context-aware escaping (e.g., ${component.value @ context='html'}).Affected if Form field templates lack proper context-aware output encoding or use unescaped variable interpolation.
-
Review custom form component implementationsIf custom form components exist under /apps/*/components, examine their JavaSightly templates and any associated Java/JS controllers for input validation and output encoding. Search for direct output of request parameters or form field values without sanitization.Affected if Custom form components output user-submitted data without encoding or validation.
-
Check for existing XSS filters or WCM policiesInspect the AEM editable template policies for form components under /conf, and check if global XSS protection filters (such as the AEM XSS API) are being invoked in the form templates.Affected if Form components rely on user input without invoking AEM's XSS protection APIs.
A user is affected if they run AEM 6.5.22.0 or earlier and have form components (especially Adaptive Forms or custom ones) that output user-submitted data 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 · scopedImplement output encoding and input validation/sanitization on all form fields in AEM to neutralize malicious script payloads. Consider upgrading to a patched version if released by Adobe.
AEM 6.5.23.0 or later / Feature Pack FP11.5 or later
- 1. Identify the current Adobe Experience Manager version by navigating to /system/console/configMgr or checking the 'About Adobe Experience Manager' page in the welcome screen
- 2. Confirm the installed Feature Pack (FP) version by reviewing the release notes or system information
- 3. Download and install the latest available Feature Pack (FP) that is newer than FP11.4, or the latest Cumulative Fix Pack (CFP) for AEM 6.5
- 4. Alternatively, upgrade to AEM 6.5.23.0 or later if available, which includes the fix for this vulnerability
- 5. After upgrading, clear the AEM cache and repository to ensure the patched code is fully active
- 6. Verify the fix by testing the form fields mentioned in the vulnerability to confirm malicious scripts are no longer executable
- 7. Review user permissions and implement input validation for form fields as an additional security measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49547 — 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-49547 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