Authenticated SSRF via unrestricted outbound API requests
Published Sep 22, 2025 · Updated Sep 22, 2025
Server-side request forgery in Publitio 2.2.1 and earlier allows remote authenticated users to send requests to arbitrary locations. Public records do not identify the affected endpoint or function; the vendor changelog says 2.2.2 added URL allowlist validation for API calls and tightened cURL behavior. Contributor-level access is sufficient, and the requests originate from WordPress and can query or modify internal services.
Summary
What happened
Server-side request forgery in Publitio 2.2.1 and earlier allows remote authenticated users to send requests to arbitrary locations. Public records do not identify the affected endpoint or function; the vendor changelog says 2.2.2 added URL allowlist validation for API calls and tightened cURL behavior. Contributor-level access is sufficient, and the requests originate from WordPress and can query or modify internal services.
The record
- CVE
- CVE-2025-58962
- Published
- Sep 22, 2025
- Updated
- Sep 22, 2025
- Vendor
- Publitio
- Product
- Publitio
- Classifications
- CWE-918, CAPEC-664, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 22, 2025CVE publishedPublication date reported by the CVE source.
- Sep 22, 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=n/a <=2.2.1 changes=[{"at":"2.2.2","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