Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-70060: n/a

0
Medium
VulnerabilityCVE-2025-70060cvecve-2025-70060
Published: Mon Mar 09 2026 (03/09/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

An issue pertaining to CWE-79: Improper Neutralization of Input During Web Page Generation was discovered in YMFE yapi v1.12.0.

AI-Powered Analysis

AILast updated: 03/09/2026, 16:19:24 UTC

Technical Analysis

CVE-2025-70060 is a security vulnerability discovered in YMFE yapi version 1.12.0, categorized under CWE-79, which pertains to improper neutralization of input during web page generation, commonly known as Cross-Site Scripting (XSS). This vulnerability arises when user-supplied input is not correctly sanitized or encoded before being incorporated into dynamically generated web pages, allowing attackers to inject malicious scripts. These scripts execute in the context of the victim's browser, potentially enabling theft of session cookies, redirection to malicious sites, or unauthorized actions performed on behalf of the user. YMFE yapi is a popular API management and documentation platform used by developers to streamline API lifecycle processes. The vulnerability does not currently have a CVSS score or publicly available patches, and no exploits have been reported in the wild as of the publication date. The issue likely stems from insufficient input validation or output encoding mechanisms within the web interface of YMFE yapi. Attackers can exploit this flaw by crafting malicious payloads that, when rendered by a victim's browser, execute arbitrary JavaScript code. This can compromise confidentiality and integrity of user data and may lead to further system compromise if leveraged in chained attacks. The vulnerability affects all deployments running version 1.12.0 of YMFE yapi that have not applied any mitigations. Due to the nature of XSS vulnerabilities, exploitation does not require authentication but does require user interaction (e.g., victim visiting a malicious link).

Potential Impact

The impact of CVE-2025-70060 on organizations worldwide can be significant, especially for those relying on YMFE yapi for API management and documentation. Successful exploitation can lead to theft of sensitive user information such as session tokens, enabling attackers to impersonate legitimate users and gain unauthorized access. This can result in data breaches, unauthorized API calls, and manipulation of API documentation or configurations. Additionally, attackers may use the vulnerability to deliver malware or conduct phishing attacks by injecting malicious scripts into trusted web pages. The compromise of API management platforms can disrupt development workflows, delay deployments, and damage organizational reputation. Since the vulnerability affects web interfaces, it can impact any user interacting with the affected system, broadening the scope of potential victims. The absence of known exploits currently reduces immediate risk but does not diminish the urgency for remediation, as public disclosure may prompt attackers to develop exploits. Organizations with internet-facing instances of YMFE yapi are particularly at risk, as external attackers can attempt to exploit the vulnerability remotely.

Mitigation Recommendations

To mitigate CVE-2025-70060, organizations should implement the following specific measures: 1) Monitor YMFE yapi vendor communications closely for official patches or updates addressing this vulnerability and apply them promptly. 2) In the absence of patches, implement strict input validation on all user-supplied data, ensuring that potentially dangerous characters are either rejected or properly encoded before rendering. 3) Employ output encoding techniques such as HTML entity encoding to neutralize scripts embedded in user inputs. 4) Configure Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks. 5) Conduct code reviews and security testing focused on input handling and output rendering in the affected application. 6) Educate users about the risks of clicking on untrusted links or submitting unverified data. 7) Consider deploying Web Application Firewalls (WAFs) with rules designed to detect and block XSS attack patterns targeting the YMFE yapi interface. 8) Limit access to the YMFE yapi interface to trusted networks or VPNs where feasible to reduce exposure. These targeted actions go beyond generic advice by focusing on the specific nature of the vulnerability and the affected product.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2026-01-09T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69aef0552904315ca31e4b39

Added to database: 3/9/2026, 4:07:49 PM

Last enriched: 3/9/2026, 4:19:24 PM

Last updated: 3/9/2026, 6:53:15 PM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses