CVE-2025-7874 is a medium (CVSS 5.3) information disclosure 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 /env.jsp.
No fixed version is named in the record or the write-up.
The write-up says env.jsp can be opened without logging in and shows the server name, the Java version and absolute file paths. It also describes a debug.jsp page that lacks authentication, where an unauthenticated visitor can change debug settings and read server logs. The debug.jsp finding is part of the write-up and is not what this CVE record describes, so check for it separately.
The record's CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, a score of 5.3. The record says the vendor was contacted early and did not respond in any way.
The record's kev flag is false, so the CVE is not in CISA's Known Exploited Vulnerabilities catalog at the time of this review.
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 "env.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.
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 which version.
- Block env.jsp and debug.jsp at the reverse proxy or web server.
- Review server logs for requests to those pages from outside your network.
- Remove the product from the internet and require VPN access.
- Ask the vendor for a fixed build.
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-200 (exposure of sensitive information), CWE-284 (improper access control). A page that shows paths, versions and logs hands an attacker the map for the next step. Diagnostic pages should be removed from production or protected like administrative pages.
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-7874?
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-7874 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-7874
- Public write-up on GitHub
- NVD record data for CVE-2025-7874, published 2025-07-20, source cna@vuldb.com
Last reviewed: 18 October 2026.
