Unauthenticated geocode changes via missing authorization
Published Apr 17, 2025 · Updated Apr 28, 2026
Missing authorization in Code for Recovery 12 Step Meeting List 3.16.5 and earlier allows remote attackers to alter geocodes. The geocode-editing path accepts unauthenticated requests and changes location coordinates without verifying authorization. No account or user interaction is required; successful exploitation can corrupt meeting locations displayed by the site.
Summary
What happened
Missing authorization in Code for Recovery 12 Step Meeting List 3.16.5 and earlier allows remote attackers to alter geocodes. The geocode-editing path accepts unauthenticated requests and changes location coordinates without verifying authorization. No account or user interaction is required; successful exploitation can corrupt meeting locations displayed by the site.
The record
- CVE
- CVE-2025-24583
- Published
- Apr 17, 2025
- Updated
- Apr 28, 2026
- Vendor
- Code for Recovery
- Product
- 12 Step Meeting List
- Classifications
- CWE-862, CAPEC-180
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.16.5 changes=[{"at":"3.16.6","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo