CVE-2025-7879 is a medium (CVSS 6.3) unrestricted file upload in Metasoft MetaCRM (MetaCRM up to 6.4.2). The record names no fixed version, so plan on isolating or replacing it. Do not expose the product to untrusted networks until you have confirmed a fix.
What's affected
The record lists MetaCRM up to 6.4.2 as affected. The vulnerable code is in mobileupload.jsp, through the File argument.
No fixed version is named in the record or the write-up.
The write-up says the extension of an uploaded file is not validated, so files are written to the server without restriction, and that the response reveals where the file was stored. That second detail matters because an attacker who can upload a file and learn its location has what they need to request it back.
The record's CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, a score of 6.3. The record says the vendor was contacted early and did not respond in any way.
The record also says the exploit has been disclosed to the public and may be used. That is not the same as confirmed attacks: this CVE is not in CISA's Known Exploited Vulnerabilities catalog (the record's kev flag is false).
How to check if you're exposed
Find out whether the component is deployed in your estate. These products often arrive inside a larger system, so check your server inventory and your web application directories:
find / -name "mobileupload.jsp" -not -path "/proc/*" 2>/dev/null | head
Then check your web server or reverse proxy logs for requests to that path from addresses you do not recognize.
For upload flaws, also look at the upload storage directory for files with script extensions that you did not put there.
A free in-browser dependency scan at gold.safeguard.sh/scan can show whether this CVE appears in a project's dependency list. Note that it covers packages. Stand-alone applications and firmware are best checked against your own inventory.
What to do now
- Confirm whether you run MetaCRM and in which version.
- Block the upload endpoint at the web server or WAF until a fix exists.
- Make sure uploaded files cannot be executed: store them outside the web root, or disable script handling in the upload directory.
- Search the upload directory for files with script extensions and review anything unexpected.
- Check the vendor site for a newer release, and restrict the product to authenticated users on a trusted network.
If you maintain a codebase and want to know whether a vulnerable package is actually called, Safeguard's reachability analysis separates packages that are present from code paths that are used.
Why it matters
The weakness class here is CWE-284 (improper access control), CWE-434 (unrestricted upload of a dangerous file type). When an application stores a file with its original extension in a place the web server will execute, an upload becomes a way to run code. The standard defenses are an allow list of file types, a server generated name, storage outside the web root and no script execution in the upload folder.
MetaCRM has several public findings against it from the same researcher, and the vendor did not respond, per the record. Treat the product as one that needs network isolation, not a series of one off patches.
Quick check
Is there a patch for CVE-2025-7879?
The record does not name a fixed version, and for PAD CMS CERT Polska says none will be published. Treat the product as unpatched, reduce its exposure and check the vendor or project site for news.
Is CVE-2025-7879 being exploited in the wild?
The record's kev flag is false, so it is not in CISA's Known Exploited Vulnerabilities catalog. The record does say the exploit has been disclosed to the public, so assume attackers can find it.
Sources
- Safeguard Gold entry for CVE-2025-7879
- Public write-up on GitHub
- NVD record data for CVE-2025-7879, published 2025-07-20, source cna@vuldb.com
Last reviewed: 18 October 2026.
