dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-7487

MEDIUM · 6.3 CVSS v3.1 Published 2025-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Unrestricted file upload vulnerability in JoeyBling SpringBoot_MyBatisPlus SysFileController at /file/upload endpoint. The portraitFile parameter lacks proper validation, allowing attackers to upload arbitrary files including executable content. This is a remote attack vector with public exploit availability.

MitigationImplement strict file type validation (allowlist approach), verify file content/magic bytes, store uploads outside webroot with randomized filenames, and disable script execution in the upload directory.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if JoeyBling SpringBoot_MyBatisPlus application is deployed
    Check for presence of JAR/WAR files, application logs, or running Java processes containing 'SpringBoot_MyBatisPlus' or 'JoeyBling' in the path or process arguments. Inspect web server access logs for requests to /file/upload endpoint.
    Affected if The application is present and the upload endpoint is accessible from the network
  2. Determine the installed version
    Locate the application JAR/WAR file and check its filename for version strings, or examine pom.xml/build.gradle if source code is available. Check application startup logs for version information.
    Affected if Version cannot be determined or is within an unpatched release
  3. Verify if the /file/upload endpoint is exposed
    Send a test HTTP request to POST /file/upload (or inspect proxy/waf logs for such requests). Confirm the endpoint responds and accepts multipart/form-data.
    Affected if The endpoint is reachable and processes upload requests
  4. Confirm portraitFile parameter acceptance
    Send a multipart POST request with a portraitFile parameter to /file/upload. Inspect the application response or server logs to confirm the parameter is processed without rejection.
    Affected if The portraitFile parameter is accepted without validation errors
  5. Check for file type validation on uploads
    Review the SysFileController source code (if accessible) or attempt uploading files with executable extensions (.jsp, .exe, .php) and non-image extensions. Inspect the response and verify if uploads are stored with their original extensions.
    Affected if Files with executable extensions are accepted and stored without content-type validation or extension blocking

You are affected if the JoeyBling SpringBoot_MyBatisPlus application is running with the /file/upload endpoint exposed and the portraitFile parameter accepts files without proper validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict file type validation (allowlist approach), verify file content/magic bytes, store uploads outside webroot with randomized filenames, and disable script execution in the upload directory.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7487 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7487 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data