CVE-2026-16324 MetaCRM vulnerability
A vulnerability was identified in Metasoft 美特软件 MetaCRM up to 6.4.0 Beta06. The impacted element is an unknown function of the file /business/qnaire/upload.jsp. Such manipulation of the argument File leads to unrestricted upload. The attack may be launched remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
Browse Authorization Bypass security risksQuick answer
Metasoft 美特软件 MetaCRM should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- 6.4.0 Beta06
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-16324 affects MetaCRM and involves unsafe file upload. Successful exploitation may place untrusted files on the server and can lead to data exposure, content changes, or code execution. Treat this as a high-priority fix, especially when the affected component or endpoint is reachable by untrusted users. No confirmed fixed MetaCRM release is recorded. Block business/qnaire/upload.jsp from untrusted users, enforce file-type and storage controls, and migrate to a vendor-supported patched release before restoring uploads.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses MetaCRM.
- Compare the installed version with the recorded affected range: 6.4.0 Beta06.
- No confirmed fixed MetaCRM release is recorded. Block business/qnaire/upload.jsp from untrusted users, enforce file-type and storage controls, and migrate to a vendor-supported patched release before restoring uploads.
- Until patched, disable the affected upload path or require authentication, strict file allowlists, non-executable storage, and server-side content checks.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to MetaCRM; remove access that is not required.
- Review upload directories, web logs, process activity, and file-integrity alerts for unexpected files, scripts, or execution attempts.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-16324 in place.
- Use a safe regression test to confirm the affected unsafe file upload path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-16324?
Metasoft 美特软件 MetaCRM versions listed as affected should be reviewed: 6.4.0 Beta06.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.