Authenticated SSRF to arbitrary domains
Published Dec 7, 2023 · Updated Apr 28, 2026
SSRF in Code for Recovery 12 Step Meeting List 3.14.24 and earlier allows remote authenticated users to send server-side requests. Patchstack and the upstream changelog identify the weakness and security release but do not disclose the affected function or how attacker-controlled URLs reach the request operation. Contributor-level access is required; successful exploitation can reach arbitrary domains and expose data returned by other services.
Summary
What happened
SSRF in Code for Recovery 12 Step Meeting List 3.14.24 and earlier allows remote authenticated users to send server-side requests. Patchstack and the upstream changelog identify the weakness and security release but do not disclose the affected function or how attacker-controlled URLs reach the request operation. Contributor-level access is required; successful exploitation can reach arbitrary domains and expose data returned by other services.
The record
- CVE
- CVE-2023-46641
- Published
- Dec 7, 2023
- Updated
- Apr 28, 2026
- Vendor
- Code for Recovery
- Product
- 12 Step Meeting List
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 7, 2023CVE 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=n/a <=3.14.24 changes=[{"at":"3.14.25","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