Publitio <= 2.2.1 - Authenticated (Contributor+) Server-Side Request Forgery
Strategic Overview
- Status
- Patched in 2.2.2
- Affected Plugin
- Publitio
- Affected Version
<= 2.2.1- CVSS
- 6.4Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2025-58962
At a glance
CVE-2025-58962 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Publitio WordPress plugin, affecting versions <= 2.2.1. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.2.2; sites on affected versions should update now. Disclosed September 2025, reported by Muhammad Yudha - DJ.
Vulnerability Overview
The Publitio plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.2.1. This makes it possible for authenticated attackers, with Contributor-level access and above, to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in Publitio <= 2.2.1 takes an account at Contributor level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Publitio the fix is 2.2.2: builds <= 2.2.1 are affected, anything from 2.2.2 onward is not.
Remediation
Update to version 2.2.2, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Publitio 2.2.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Publitio
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C