CVE-2026-91751

8.3

Flextype · Flextype CMS

Flextype CMS through 1.0.0-alpha.3 contains a path traversal vulnerability in the Entries REST API that allows authenticated API token holders to read, create, or overwrite arbitrary filesystem files.

Executive summary

An authenticated path traversal vulnerability in Flextype CMS allows attackers to read or overwrite arbitrary files on the host system, posing a critical risk to data integrity and system security.

Vulnerability

The Entries REST API fails to properly validate the id and new_id parameters, allowing an authenticated user with an API token to use directory traversal sequences to escape the intended directory and access the broader filesystem.

Business impact

Successful exploitation of this vulnerability allows an attacker to manipulate sensitive configuration files, overwrite application code, or exfiltrate private data stored on the server. Given the CVSS score of 8.3, this flaw is categorized as high severity because it enables unauthorized file system access, which could lead to a full system compromise or remote code execution depending on the files manipulated.

Remediation

Immediate Action: Update to the latest version of Flextype CMS as soon as a security patch is released by the vendor to address the improper input validation.

Proactive Monitoring: Review API access logs for anomalous requests containing directory traversal sequences, such as double dots (../) in the id or new_id parameters.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block directory traversal attempts targeting REST API endpoints.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

The ability to read or overwrite arbitrary files on a server is a critical security failure that necessitates immediate attention. Organizations utilizing Flextype CMS should restrict API token access to trusted users only and monitor the application for unauthorized file system activity until a formal patch is applied.

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by Vimalatithyann S, per the CVE Program record.