LiveActive security incident?Get immediate response
CVE Record

CVE-2021-28627: Adobe Experience Manager Server-side Request Forgery could lead to Security feature bypass

Adobe 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.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Adobe Experience Manager could let a logged-in attacker make the server contact systems that should be hidden behind the dispatcher. This is not shown as actively exploited in the provided sources, but it can weaken internal network boundaries and should be handled in normal patch cycles.

Executive priority

Treat this as a moderate-priority remediation item. It requires authentication, but it can undermine network controls around AEM and expose internal services to indirect access.

Technical view

CVE-2021-28627 is a server-side request forgery in Adobe Experience Manager Cloud Service and AEM 6.5.8.0 and earlier. With low privileges and no user interaction, an authenticated attacker could bypass dispatcher restrictions to reach blocked systems. CVSS v3.1 score is 5.4.

Likely exposure

Organizations running Adobe Experience Manager Cloud Service or AEM 6.5.8.0 and below may be exposed, especially where authenticated users can access AEM and dispatcher rules protect internal-only services.

Exploitation context

The provided sources describe authenticated, network-accessible exploitation with low attack complexity and no user interaction. CISA KEV status is false in the bundle, and no cited source states active exploitation.

Researcher notes

Evidence is limited to the CVE record and Adobe bulletin reference. The sources do not provide exploit details, proof of exploitation, or a named fixed version in the supplied bundle beyond vendor bulletin guidance.

Mitigation direction

  • Review Adobe APSB21-39 and apply the vendor-recommended AEM security update.
  • Inventory AEM Cloud Service and on-premises AEM instances for affected versions.
  • Restrict authenticated AEM access to trusted users and networks where practical.
  • Review dispatcher and internal network segmentation assumptions around AEM.
  • Monitor Adobe guidance for any later remediation details.

Validation and detection

  • Confirm whether any AEM instance is Cloud Service or version 6.5.8.0 or below.
  • Verify the applicable Adobe security bulletin has been implemented.
  • Review AEM and proxy logs for unusual authenticated requests to internal resources.
  • Confirm dispatcher-blocked systems are not reachable through AEM application paths.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-28627 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2021-28627Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AdobeExperience Managerunspecified, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.