GeoPulse IDOR lets users read other users' private locations
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
GeoPulse from 1.5.0 through 2.3.0 by tess1o contains an insecure direct object reference in GET /api/v1/places/geocoding/{id} (CWE-639). An authenticated user can enumerate sequential reverse_geocoding_location IDs to read other users' private locations, including custom place names, city, country, coordinates and bounding boxes.
Written with Claude Haiku 5.5 from the sources below · 2026-11-15
Description from the CNA
GeoPulse 1.5.0 through 2.3.0 contains an insecure direct object reference vulnerability in GET /api/v1/places/geocoding/{id} that allows authenticated users to read other users' private locations. Attackers can enumerate sequential reverse_geocoding_location ids to retrieve other users' custom place names, city, country, coordinates and bounding boxes from their history.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
The sources list no fixed version for GeoPulse.
Written with Claude Haiku 5.5 from the sources below · 2026-11-15
Timeline
- 2026-11-15 Threatist record created from CVE-2026-129467
- 2026-11-15 Alias added: GHSA-6hh5-5g4m-3g64
References
Patch 2
Sources
- CVE-2026-129467 · CVE Program
- CVE-2026-129467 · NVD
- FIRST EPSS
- GHSA-6hh5-5g4m-3g64 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences