ZeroHour
Full Disclosurepublished ()ingested
Part of a story covered by 8 sources: “Flextype CMS v1.0.0-alpha.3: Eight Disclosed Vulnerabilities Enable Auth Bypass, File Read, SSRF, and PHP Remote Code Execution” — merged summary and timeline →

Flextype v1.0.0-alpha.3 NULL access_token Authentication Bypass

lowVulnerabilityimportance 28
AI summary · glm-5.3-flash

Flextype CMS v1.0.0-alpha.3 API endpoints accept a NULL access_token because isset() validation lets requests bypass authentication.

Flextype CMS v1.0.0-alpha.3 API endpoints can declare access_token as a required parameter, but required-parameter validation only verifies the key exists in the request data. Authentication is then verified inside an isset($data['access_token']) condition, which in PHP treats a NULL value as absent. This allows requests supplying a NULL access_token to bypass authentication on affected endpoints. The flaw was disclosed on the Full Disclosure mailing list on September 3, 2026.

  • Required-parameter validation only checks key presence, not a valid non-empty token value
  • isset($data['access_token']) treats NULL as absent, allowing authentication bypass
  • No CVE identifier, patch, or exploitation evidence is referenced in the disclosure
VendorsFlextype
ProductsFlextype CMS
OrganizationsFull Disclosure
Full article

Posted by Ron E on Sep 03 Description Flextype CMS v1.0.0-alpha.3 contains an authentication validation vulnerability in the API request-processing functionality. API endpoints may declare access_token as a required parameter, but the required-parameter validation only verifies that the corresponding key exists in the supplied request data. Authentication verification is subsequently performed inside an isset($data ['access_token']) condition. In PHP, isset()...

This source does not provide full text. Read it at seclists.org.