CVE Intelligence
Critical File handling exploit reference

CVE-2025-2708 — zhijiantianya ruoyi-vue-pro Backend File Upload upload path traversal

A vulnerability was identified in zhijiantianya ruoyi-vue-pro 2.4.1. Affected is an unknown function of the file /admin-api/infra/file/upload of the component Backend File Upload Interface. Such manipulation of the argument path leads to path traversal. The attack may be performed from remote. The exploit is publicly available and might be used. The name of the patch is 4ae3f6b2c9883978837638c14e3d18419819eeb0. Applying a patch is advised to resolve this issue.

Published Mar 24, 2025 · Updated Oct 26, 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.7% (30-day exploitation probability)+8
  • Technical severity (critical)+10
  • 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.74%
ahead of 55% of scored CVEs · Oct 27, 2026
Affects
Iocoder
Ruoyi-vue-pro
CVSS base
9.1
Critical · 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 Ruoyi-vue-pro, Zhijiantianya Ruoyi-vue-pro).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Iocoder Ruoyi-vue-pro version 2.4.1 Vulnerable NIST National Vulnerability Database
Zhijiantianya Ruoyi-vue-pro version 2.4.1 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
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
9.1 CVSS 3.1 Critical 3.9 5.2 nvd@nist.gov via NIST National Vulnerability Database
5.4 CVSS 3.1 Medium 2.8 2.5 cna@vuldb.com via NIST National Vulnerability Database
5.4 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.4 CVSS 3.1 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.4 CVSS 3.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.5 CVSS 2.0 Medium 8.0 4.9 cna@vuldb.com via NIST National Vulnerability Database
5.5 CVSS 2.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 9.1 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-22 · Path Traversal

Other CVEs with this weakness →

EPSS over time FIRST

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

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).
  • Monitor file creation in web directories and paths with traversal sequences (../).
web/proxy/WAF logsnetwork IDS/IPSfile integrity (FIM)endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · zhijiantianya/ruoyi-vue-pro
    Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 26, 2026
  • Affected products added · iocoder/ruoyi-vue-pro
    Oct 26, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.1
    Oct 26, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 26, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 26, 2026 · Alertas do Telegram
  • 2025
  • CVE published
    Mar 24, 2025 · VulDB

Source activity

Repeated readings are counted rather than listed.

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

References

12 on the record

Elsewhere on this site

Iocoder
every CVE for this vendor
File handling
same class
CWE-22
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-116006 YunaiV/zhijiantianya ruoyi-vue-pro SMS Code Verification AuthController.java improper authentication 3d
  • CVE-2026-116007 YunaiV/zhijiantianya ruoyi-vue-pro SMS Code Verification SmsCodeServiceImpl.java SmsCodeServiceImpl.validateSmsCode0 excessive authentication 3d
  • CVE-2026-97324 YunaiV/zhijiantianya ruoyi-vue-pro Demo-order Payment Callback PayDemoOrderController.java updateDemoOrderPaid improper authorization Sep 24, 2026
  • CVE-2026-97325 YunaiV/zhijiantianya ruoyi-vue-pro OAuth2 Client OAuth2ClientServiceImpl.java validOAuthClientFromCache redirect Sep 24, 2026
  • CVE-2026-97320 YunaiV/zhijiantianya ruoyi-vue-pro AI Knowledge AiKnowledgeDocumentServiceImpl.java AiKnowledgeDocumentServiceImpl.readUrl server-side request forgery Sep 24, 2026
  • CVE-2026-97321 YunaiV/zhijiantianya ruoyi-vue-pro GoView Data Endpoint GoViewDataServiceImpl.java GoViewDataServiceImpl.getDataBySQL sql injection Sep 24, 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-2708 is "zhijiantianya ruoyi-vue-pro Backend File Upload upload path traversal", rated Critical. It affects Ruoyi-vue-pro (Iocoder); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.1 describes technical severity. EPSS 0.74% 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.