CVE-2021-28627
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 Cloud Service offering, as well as versions 6.5.8.0 (and below) is affected by a Server-side Request Forgery. An authenticated attacker could leverage this vulnerability to contact systems blocked by the dispatcher. Exploitation of this issue does not require user interaction.
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 contains a Server-Side Request Forgery (SSRF) vulnerability allowing authenticated attackers to make the AEM server initiate requests to internal or otherwise protected systems that the dispatcher would normally block. This bypasses network segmentation controls by leveraging the trusted server position.
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.8.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 AEM versionLocate the installed Adobe Experience Manager version through the AEM System Console at /system/console/bundles, or check the version.properties file in the crx-quickstart directory.Affected if The installed version is 6.5.8.0 or lower
-
Confirm AEM authentication is enabledVerify that user authentication is configured and operational on the AEM instance by checking the login page accessibility and user repository status.Affected if Authentication is active, as the vulnerability requires an authenticated attacker to exploit the SSRF
-
Review accessible HTTP request endpointsIdentify which AEM endpoints or servlets are exposed that handle outbound HTTP requests. Check the Sling servlet mappings and any custom endpoints under /bin/ or /services/.Affected if Endpoints capable of initiating outbound HTTP requests are accessible to authenticated users without additional validation
The environment is affected if AEM version is 6.5.8.0 or lower, authentication is enabled, and endpoints that can trigger outbound requests are accessible to authenticated 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 · scopedApply the AEM security patch (version 6.5.9.0 or higher for on-premise, or the fixed Cloud Service release) to prevent the server from making arbitrary outbound requests. Consider network segmentation and strict firewall rules as compensating controls.
AEM 6.5.9.0 or later service pack
- Obtain the latest Adobe Experience Manager 6.5 service pack or cumulative hotfix from the official Adobe Software Distribution portal
- Apply the update to your AEM instance following Adobe's standard upgrade procedures
- Verify the SSRF vulnerability is remediated by confirming the fix is applied
- Test that normal AEM functionality remains intact after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28627 — 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-2021-28627 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