Technical impact
Flagr before version 1.2.5 contains an authentication bypass that lets an unauthenticated attacker call the flag‑management write API through the insecure default whitelist. By accessing endpoints such as /api/v1/flags, the attacker can create, modify, enable, disable, and delete flags, variants, segments, constraints, and distributions, effectively taking control of application feature toggling.
Affected Systems
Affecting OpenFlagr Flagr installations prior to version 1.2.5, including 1.2.4 and earlier. The vulnerability hinges on the default FLAGR_BASIC_AUTH_WHITELIST_PATHS configuration that allows requests to the write API without proper authentication.
Risk and Exploitability
The CVSS score of 8.8 indicates high severity, and although EPSS is not available, the vulnerability can be exploited by any remote attacker who can reach the Flagr service. The default whitelist matches only path prefixes regardless of HTTP method; attackers can craft POST, PUT, or DELETE requests to /api/v1/flags and related endpoints. The issue is not currently listed in the CISA KEV catalog, but the high score and clear attack path suggest a high likelihood of exploitation.