Skip to main content
VulnerabilityPublished

CVE-2025-57266: ThriveX Blogging Framework · Improper Access Control

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

European organizations should immediately audit their use of the ThriveX Blogging Framework to identify affected versions (2.5.9 through 3.1.3). Until an official patch is released, organizations should implement the following mitigations: 1) Restrict access to the /api/assistant/list endpoint using network-level controls such as IP whitelisting or VPN access to limit exposure to trusted users only. 2) Implement Web Application Firewall (WAF) rules to detect and block unauthorized requests targeting this endpoint. 3) Rotate all API keys that may have been exposed or are accessible via this endpoint to invalidate any compromised credentials. 4) Monitor logs for unusual access patterns or attempts to access the vulnerable endpoint. 5) Consider temporarily disabling or restricting the API endpoint if feasible without impacting critical operations. 6) Stay alert for official patches or updates from ThriveX and apply them promptly once available. 7) Conduct a thorough security review of API key management practices to ensure keys are stored and transmitted securely, minimizing future exposure risks.

Description

An issue was discovered in file AssistantController.java in ThriveX Blogging Framework 2.5.9 thru 3.1.3 allowing unauthenticated attackers to gain sensitive information such as API Keys via the /api/assistant/list endpoint.

References

Community reviews

Loading reviews…