SSRF via attacker-controlled Referer URL
Published Apr 26, 2025 · Updated Apr 28, 2025
Server-side request forgery in ChurchCRM 5.16.0 allows remote attackers to make server-side requests via a crafted Referer header. The public proof of concept supplies a destination URL in the Referer header and observes the server issuing an outbound request to that URL. No authentication is required, but exploitation has high complexity; published metrics establish low-integrity impact and no confidentiality or availability impact.
Summary
What happened
Server-side request forgery in ChurchCRM 5.16.0 allows remote attackers to make server-side requests via a crafted Referer header. The public proof of concept supplies a destination URL in the Referer header and observes the server issuing an outbound request to that URL. No authentication is required, but exploitation has high complexity; published metrics establish low-integrity impact and no confidentiality or availability impact.
The record
- CVE
- CVE-2025-3954
- Published
- Apr 26, 2025
- Updated
- Apr 28, 2025
- Vendor
- ChurchCRM
- Product
- ChurchCRM
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 26, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 2025Record 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=5.16.0
What conditions does exploitation require?
What is affected?
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
- SSRF via Referrer field in ChurchCRM 5.16.0proof of concept · unverified
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