Authenticated SSRF via getUrl request handling
Published Jul 22, 2024 · Updated Apr 28, 2026
SSRF in Seraphinite Solutions Seraphinite Post .DOCX Source 2.16.9 and earlier allows remote authenticated users to trigger server-side requests. The vendor identifies getUrl as the affected function but has not published how it mishandles untrusted URLs or restricts request destinations. Subscriber-level access is required; successful exploitation makes the WordPress server contact an attacker-selected destination.
Summary
What happened
SSRF in Seraphinite Solutions Seraphinite Post .DOCX Source 2.16.9 and earlier allows remote authenticated users to trigger server-side requests. The vendor identifies getUrl as the affected function but has not published how it mishandles untrusted URLs or restricts request destinations. Subscriber-level access is required; successful exploitation makes the WordPress server contact an attacker-selected destination.
The record
- CVE
- CVE-2024-38728
- Published
- Jul 22, 2024
- Updated
- Apr 28, 2026
- Vendor
- Seraphinite Solutions
- Product
- Seraphinite Post .DOCX Source
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 22, 2024CVE 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 <=2.16.9
- Affected versionversion=n/a <=2.16.9 changes=[{"at":"2.16.10","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