CVE Intelligence
High exploit reference

CVE-2025-10275 — YunaiV yudao-cloud transfer improper authorization

A weakness has been identified in YunaiV yudao-cloud up to 2025.09. This affects an unknown part of the file /crm/business/transfer. Executing a manipulation of the argument ids/newOwnerUserId can lead to improper authorization. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks. It is recommended to upgrade the affected component. The vendor confirms: "[T]he current code already checks the functional update permission, uses the authenticated server-side user ID, requires CRM OWNER permission, and explicitly rejects non-owner transfers in the shared transfer service, except for authorized CRM administrators."

Published Sep 11, 2025 · Updated Oct 27, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (high)+6
  • CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.3%
ahead of 23% of scored CVEs · Oct 27, 2026
Affects
Iocoder
Yudao-cloud
CVSS base
8.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Iocoder Yudao-cloud, YunaiV Yudao-cloud).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Iocoder Yudao-cloud ≤ 2025.09 Vulnerable NIST National Vulnerability Database
YunaiV Yudao-cloud version 2025.09 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 4.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
2.1 CVSS 4.0 Low — — cna@vuldb.com via NIST National Vulnerability Database
8.8 CVSS 3.1 High 2.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
6.3 CVSS 3.1 Medium 2.8 3.4 cna@vuldb.com via NIST National Vulnerability Database
6.3 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
6.3 CVSS 3.1 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
6.3 CVSS 3.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
6.5 CVSS 2.0 Medium 8.0 6.4 cna@vuldb.com via NIST National Vulnerability Database
6.5 CVSS 2.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 8.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-266

Other CVEs with this weakness →

EPSS over time FIRST

Oct 26, 2026 → Oct 27, 2026 · 2 reading(s) · max 0.33%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · yunaiv/yudao-cloud
    Oct 27, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 27, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 27, 2026
  • Affected products added · iocoder/yudao-cloud
    Oct 27, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.8
    Oct 27, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 27, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 27, 2026 · Alertas do Telegram
  • 2025
  • CVE published
    Sep 11, 2025 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 27, 2026 – Oct 27, 2026
  • 1× Official description updated · Oct 27, 2026 – Oct 27, 2026

References

10 on the record

Elsewhere on this site

Iocoder
every CVE for this vendor
CWE-266
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-116015 yudao-cloud through 2026.09 IDOR via after-sale-log list endpoint 3d
  • CVE-2026-116016 yudao-cloud through 2026.09 Data Permission Bypass via data-permission-enable Header 3d
  • CVE-2026-58448 yudao-cloud < 2026.06 - BPM Module Broken Access Control via process-instance API Jun 30, 2026
  • CVE-2026-9464 YunaiV yudao-cloud Admin API Endpoint create IotDataSinkHttpConfig server-side request forgery May 25, 2026
  • CVE-2026-7710 YunaiV yudao-cloud Ruoyi-Vue-Pro JwtAuthenticationTokenFilter.java doFilterInternal improper authentication May 3, 2026
  • CVE-2026-7678 YunaiV yudao-cloud GoViewDataServiceImpl.java getDataBySQL sql injection May 3, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-10275 is "YunaiV yudao-cloud transfer improper authorization", rated High. It affects Yudao-cloud (Iocoder); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.30% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.