VulnerabilityPublished 12 Jul 2025Updated 14 Jul 2025

CVE-2025-7487: JoeyBling SpringBoot_MyBatisPlus · Unrestricted Upload

Affects JoeyBling SpringBoot_MyBatisPlusSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

European organizations should implement immediate compensating controls while awaiting official patches. These include: 1) Restricting access to the /file/upload endpoint via network-level controls such as firewalls or web application firewalls (WAF) with rules to detect and block suspicious upload attempts. 2) Implement strict server-side validation of uploaded files, enforcing allowed file types, size limits, and scanning for malware. 3) Employ application-layer authentication and authorization to ensure only legitimate users can upload files. 4) Monitor logs and network traffic for unusual upload activity or anomalies. 5) Isolate the file upload functionality in a sandboxed environment or separate server to limit potential damage. 6) Conduct thorough code reviews and penetration testing focused on file upload mechanisms. 7) Engage with the vendor or community to obtain updates or patches as soon as they become available, and prioritize their deployment. 8) Educate developers and administrators about secure file handling practices to prevent similar vulnerabilities. These measures go beyond generic advice by focusing on immediate risk reduction and operational controls tailored to the vulnerability's characteristics.

Description

A vulnerability, which was classified as critical, was found in JoeyBling SpringBoot_MyBatisPlus up to a6a825513bd688f717dbae3a196bc9c9622fea26. This affects the function SysFileController of the file /file/upload. The manipulation of the argument portraitFile leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.

Impact

For European organizations using JoeyBling SpringBoot_MyBatisPlus, this vulnerability poses a significant risk. Exploitation could lead to unauthorized access, data breaches, and service disruption. Attackers could upload malicious web shells or scripts, enabling persistent access and lateral movement within corporate networks. This can compromise sensitive data, including personal data protected under GDPR, leading to regulatory penalties and reputational damage. The medium CVSS score suggests limited direct impact on confidentiality, integrity, and availability, but the unrestricted upload capability can be leveraged for more severe attacks depending on the environment. Organizations relying on this framework for critical business applications or customer-facing services are at higher risk. The lack of authentication and user interaction requirements means automated attacks and mass scanning campaigns could target vulnerable systems across Europe. Additionally, the rolling release nature of the software may delay patch deployment, increasing exposure time. The threat is exacerbated if organizations have weak internal network segmentation or insufficient monitoring of file upload endpoints.

Summary

CVE-2025-7487 is a critical vulnerability identified in the JoeyBling SpringBoot_MyBatisPlus framework, specifically affecting the SysFileController component's /file/upload endpoint. The vulnerability arises from improper validation and handling of the 'portraitFile' argument, which allows an attacker to perform an unrestricted file upload. This means that an attacker can remotely upload arbitrary files to the server without authentication or user interaction. The unrestricted upload can lead to remote code execution, server compromise, or deployment of malicious payloads, depending on the server configuration and file handling mechanisms. The vulnerability exists in versions up to commit a6a825513bd688f717dbae3a196bc9c9622fea26, but due to the product's rolling release model, exact versioning is unclear. The CVSS 4.0 base score is 5.3 (medium severity), reflecting network attack vector, low attack complexity, no privileges or user interaction required, but limited impact on confidentiality, integrity, and availability. Although no known exploits are currently observed in the wild, the public disclosure of the exploit increases the risk of exploitation. The vulnerability's root cause is insufficient input validation and lack of restrictions on file types and sizes during upload, which is a common security flaw in web applications handling file uploads. This vulnerability is particularly dangerous because it can be exploited remotely without authentication, making it accessible to a wide range of threat actors. The continuous delivery model of the product complicates patch management and version tracking, potentially delaying mitigation efforts.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 19 Jul 2025, 21:02 UTC

Technical details

References

Community reviews

Related threats