phpIPAM < 1.8.2 Authentication Bypass via REST API Object Cache
48Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 9.3epss 0.4%
from disclosure to weapon3 days
Published on NVDAug 24
1st PoC+3d
exploitation probability
0.4%top 72% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
phpIPAM before 1.8.2 contains an authentication bypass vulnerability in the REST API that allows unauthenticated attackers to gain full API access by exploiting an insecure object cache keying mechanism. The cache is keyed by lookup value alone without including the searched column, enabling an entry written during an app_id lookup to satisfy a subsequent app_code lookup, allowing attackers to use the numeric database row identifier as an API token to read, write, and delete all IP address management records.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Affected products
phpipam · phpipampublic PoCs found — 1
githubgithub.com/Hunt-Benito/the-token-was-a-row-number-cve-2026-67602-phpipam-rest-api-authentication-bypass★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.