CVE-2021-41792
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 · uneditedAn issue was discovered in Hyland org.alfresco:alfresco-content-services through 6.2.2.18 and org.alfresco:alfresco-transform-services through 1.3. A crafted HTML file, once uploaded, could trigger an unexpected request by the transformation engine. The response to the request is not available to the attacker, i.e., this is blind SSRF.
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 confidenceA blind Server-Side Request Forgery (SSRF) vulnerability in Alfresco Content Services and Transform Services allows attackers to upload crafted HTML files that trigger the transformation engine to make arbitrary requests to internal or external resources. Since this is blind SSRF, the attacker cannot directly view the response, but can still potentially probe internal services or exfiltrate data through the forced requests.
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>= 5.0.0.0, <= 5.2.7.11>= 6.0.0.0, <= 6.0.1.9>= 6.1.1.0, <= 6.1.1.10>= 6.2.0.0, <= 6.2.2.18<= 1.3CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Alfresco Content Services versionCheck the installed version via the admin console, war file manifest, or version.properties file in the Alfresco installation directoryAffected if Version is 5.0.0.0-5.2.7.11, 6.0.0.0-6.0.1.9, 6.1.1.0-6.1.1.10, or 6.2.0.0-6.2.2.18
-
Identify Alfresco Transform Services versionCheck the transform service installation for its version number in the service properties or configuration filesAffected if Version is 1.3 or lower
-
Verify if transformation engine is accessibleConfirm whether the Transform Service endpoint is exposed and reachable by untrusted users or anonymous callersAffected if The transformation endpoint accepts requests from untrusted sources without authentication or strict authorization
-
Check HTML file upload capabilityDetermine if the system permits users to upload HTML files through the content services upload interfaceAffected if Users can upload HTML files to the system
-
Review outbound network restrictionsInspect firewall rules, network policies, or transform service configuration to determine if outbound HTTP/HTTPS requests are unrestrictedAffected if The transform service can initiate outbound requests to arbitrary internal or external URLs
Your environment is affected if you run any affected version of Alfresco Content Services (5.0.0.0-5.2.7.11, 6.0.0.0-6.0.1.9, 6.1.1.0-6.1.1.10, or 6.2.0.0-6.2.2.18) or Transform Services (1.3 or lower), and the transformation engine accepts requests from users or processes untrusted HTML content without strict validation or network isolation.
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.
From vendor dataImplement strict input validation on uploaded HTML files to sanitize or reject malicious content, and apply network segmentation to restrict the transformation engine's ability to make outbound requests to internal infrastructure.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41792 — 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-41792 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