CVE-2026-129467
Received Received - Intake

Insecure Direct Object Reference in GeoPulse Places API

Vulnerability report for CVE-2026-129467, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-15

Last updated on: 2026-11-15

Assigner: VulnCheck

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-15
Last Modified
2026-11-15
Generated
2026-11-15
AI Q&A
2026-11-15
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
tess1o GeoPulse From 1.5.0 (inc) to 2.3.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an Insecure Direct Object Reference (IDOR) in GeoPulse 1.5.0 through 2.3.0. It allows authenticated users to read other users' private locations by exploiting predictable IDs in the GET /api/v1/places/geocoding/{id} endpoint. Attackers can enumerate sequential IDs to retrieve sensitive data like custom place names, city, country, coordinates, and bounding boxes from other users' location histories.

Detection Guidance

To detect this IDOR vulnerability, monitor API logs for repeated GET requests to /api/v1/places/geocoding/{id} with sequential numeric IDs. Check for unauthorized access patterns where users retrieve location data not belonging to them. Use tools like Burp Suite or OWASP ZAP to intercept and manipulate API requests, testing for improper authorization checks.

Impact Analysis

If you use GeoPulse 1.5.0 through 2.3.0, an attacker with an authenticated account could access your private location data, including custom place labels, coordinates, and city/country information. This could expose your location history and personal place names to unauthorized users. The attack requires only a standard user role and no special privileges.

Compliance Impact

This vulnerability could lead to non-compliance with privacy regulations like GDPR and HIPAA by exposing users' location data without authorization. GDPR requires protecting personal data, and HIPAA mandates safeguarding health-related location information. The unauthorized access to private locations may violate these regulations.

Mitigation Strategies

Immediately update GeoPulse to the latest patched version where the fix has been applied. If patching is not possible, implement server-side checks in the PlaceDetailsService to verify that the requested location ID belongs to the authenticated user before returning data. Restrict API access to authenticated users only and log suspicious enumeration attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-129467. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...