LiveActive security incident?Get immediate response
CVE Record

CVE-2021-43449: ONLYOFFICE all versions as of 2021-11-08 is vulnerable to Server-Side Request Forgery (SSRF).

ONLYOFFICE all versions as of 2021-11-08 is vulnerable to Server-Side Request Forgery (SSRF). The document editor service can be abused to read and serve arbitrary URLs as a document.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

ONLYOFFICE document editor could be abused to make the server fetch and return arbitrary URLs as documents. That matters because an attacker may use a trusted document service to reach internal or sensitive web resources. The bundle does not prove active exploitation or identify a vendor patch.

Executive priority

Treat this as high priority for exposed ONLYOFFICE deployments, especially those with internal network reach. The business risk is data exposure through a trusted collaboration service. Prioritize inventory, exposure reduction, vendor guidance review, and monitoring.

Technical view

CVE-2021-43449 is an SSRF in ONLYOFFICE, described as affecting all versions as of 2021-11-08. The vector is network-accessible with low complexity, no privileges, and user interaction required. The CVSS score is 8.1, with high confidentiality and integrity impact and no availability impact.

Likely exposure

Exposure is most likely where ONLYOFFICE document editor services are internet-facing, embedded in collaboration portals, or able to make outbound requests to internal networks. Exact affected products and versions are not enumerated in the source bundle beyond the 2021-11-08 date statement.

Exploitation context

The bundle cites public research and the CVE record, but CISA KEV status is false and no cited source here confirms active exploitation. The described weakness is SSRF: abusing document fetching behavior to access arbitrary URLs through the server.

Researcher notes

Evidence is incomplete on exact package names, fixed versions, and exploitation in the wild. The strongest source-grounded points are SSRF behavior, broad date-based affected statement, CVSS 8.1, and no KEV listing in the supplied bundle.

Mitigation direction

  • Check ONLYOFFICE vendor guidance for fixed versions or configuration changes.
  • Inventory and upgrade affected ONLYOFFICE deployments if a vendor fix is available.
  • Restrict document editor access to trusted users and trusted network paths.
  • Limit outbound network access from the document editor service.
  • Monitor for unusual outbound URL fetches from ONLYOFFICE hosts.

Validation and detection

  • Identify all ONLYOFFICE deployments and record version/build dates.
  • Confirm whether document editor services can reach internal-only URLs.
  • Review outbound proxy, firewall, and application logs for anomalous fetches.
  • Verify internet exposure and authentication controls around document editor endpoints.
  • Track vendor advisories until an affected-version and fix statement is confirmed.
Prepared
Confidence
medium
Sources
5

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-43449 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
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

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

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
4Source 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
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N2.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2021-43449Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
n/an/an/aListed
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.