LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25870: DoraCMS <= 3.1 UEditor Remote Image Fetch SSRF

DoraCMS version 3.1 and prior contains a server-side request forgery (SSRF) vulnerability in its UEditor remote image fetch functionality. The application accepts user-supplied URLs and performs server-side HTTP or HTTPS requests without sufficient validation or destination restrictions. The implementation does not enforce allowlists, block internal or private IP address ranges, or apply request timeouts or response size limits. An attacker can abuse this behavior to induce the server to issue outbound requests to arbitrary hosts, including internal network resources, potentially enabling internal network scanning and denial of service through resource exhaustion.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

DoraCMS 3.1 and earlier can be tricked into making server-side web requests through UEditor remote image fetching. That can let an attacker reach systems the attacker cannot access directly, including internal services, and may create resource-exhaustion risk.

Executive priority

Treat this as a moderate-priority exposure review for any public DoraCMS site. Prioritize systems with network access to sensitive internal services, because SSRF can turn a web server into a bridge into protected environments.

Technical view

The issue is CWE-918 SSRF in DoraCMS UEditor remote image fetch. User-supplied HTTP/HTTPS URLs are fetched without sufficient destination validation, allowlists, private-IP blocking, timeout controls, or response-size limits. The CVSS 4.0 score is 6.9.

Likely exposure

Exposure is likely limited to internet-reachable DoraCMS deployments using affected UEditor remote image fetch functionality. The source bundle names DoraCMS 3.1 and prior, but the structured affected-version metadata appears incomplete.

Exploitation context

The bundle does not identify active exploitation, and KEV status is false. The described risk is unauthenticated network exploitation that induces outbound requests from the server, potentially supporting internal probing or denial of service.

Researcher notes

Key evidence comes from the CVE description, GitHub issue, DoraCMS product reference, and VulnCheck advisory. Evidence is incomplete on exact fixed versions and official remediation, so validation should avoid assuming a patch exists.

Mitigation direction

  • Check DoraCMS vendor guidance and the linked advisory for any official fix or upgrade path.
  • Disable or restrict UEditor remote image fetching if it is not required.
  • Apply outbound egress filtering from DoraCMS hosts to internal and private address ranges.
  • Use URL allowlists, request timeouts, and response-size limits where configurable.
  • Monitor server outbound traffic for unexpected internal destinations.

Validation and detection

  • Inventory DoraCMS deployments and confirm whether version 3.1 or earlier is present.
  • Determine whether UEditor remote image fetching is enabled or reachable by untrusted users.
  • Review proxy, firewall, and application logs for unusual outbound requests from DoraCMS hosts.
  • Confirm egress controls block access to private, loopback, link-local, and metadata endpoints.
  • Track the GitHub issue and advisory for corrected affected-version or patch details.
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-2026-25870 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
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA: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.

2CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

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
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:LVulnCheck
5.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N3.91.4VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-25870Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
doramartDoraCMS0unknown
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.