CVE-2025-58962
BaseFortify
Publication date: 2025-09-22
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| publitio | publitio_plugin | 2.2.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Server-Side Request Forgery (SSRF) in the WordPress Publitio Plugin versions up to 2.2.1. It allows an attacker with Contributor-level access to manipulate the website into making HTTP requests to arbitrary domains controlled by the attacker. This can lead to exposure of sensitive information from other services running on the same system. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow an attacker to make the server send requests to arbitrary domains, potentially exposing sensitive information from other services on the same system. Although the risk is considered low severity and requires some level of access, it can still lead to information disclosure and unauthorized interactions with internal services. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this SSRF vulnerability involves monitoring for unusual HTTP requests originating from the Publitio plugin, especially requests to arbitrary or unexpected external domains. Since exploitation requires Contributor-level access, reviewing WordPress user activity logs for suspicious behavior is recommended. Specific commands are not provided in the resources, but network monitoring tools like tcpdump or Wireshark can be used to capture outgoing HTTP requests for analysis. Additionally, checking the plugin version installed (should be 2.2.1 or earlier if vulnerable) can be done via WordPress CLI commands such as 'wp plugin list' to identify if the vulnerable version is in use. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Publitio WordPress plugin to version 2.2.2 or later, where the vulnerability is fixed. As an interim measure, Patchstack offers virtual patching (vPatching) that automatically protects against this vulnerability even before official patches are applied. Additionally, restricting Contributor-level access to trusted users and monitoring for suspicious activity can help reduce risk until the update is applied. [1]