Read the docs

GeoPulse IDOR lets users read other users' private locations

Priority LOW 23CWE-639Published · Updated

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

EPSS 0.00218 12th percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
tess1oGeoPulse1.5.0 – 2.3.0—No fix listedCNA
  • GeoPulse Vendortess1o Affected 1.5.0 – 2.3.0 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for GeoPulse.

Written with Claude Haiku 5.5 from the sources below · 2026-11-15

Timeline

  1. 2026-11-15 Threatist record created from CVE-2026-129467
  2. 2026-11-15 Alias added: GHSA-6hh5-5g4m-3g64

References

Sources