CVE-2025-58203: WordPress Solace Extra Plugin <= 1.3.2 - Server Side Request Forgery (SSRF) Vulnerability
Server-Side Request Forgery (SSRF) vulnerability in solacewp Solace Extra solace-extra allows Server Side Request Forgery.This issue affects Solace Extra: from n/a through <= 1.3.2.
Security readout for executives and security teams
Plain-English summary
CVE-2025-58203 is an SSRF issue in the WordPress Solace Extra plugin through version 1.3.2. A highly privileged authenticated user could make the server send unintended requests, potentially exposing limited internal information or influencing requests. Public sources rate it medium severity. No cited source or KEV entry indicates active exploitation.
Executive priority
Prioritize for WordPress environments using Solace Extra, especially public business sites or sites with many administrators. The business risk is moderate because high privileges are required, but SSRF can expose internal services or data paths if abused.
Technical view
The issue is CWE-918 server-side request forgery in solacewp Solace Extra, package solace-extra. CVSS 3.1 is 4.4: network reachable, high attack complexity, high privileges required, no user interaction, scope changed, low confidentiality and integrity impact, no availability impact. Affected versions are described as through <=1.3.2.
Likely exposure
Exposure is limited to WordPress sites with Solace Extra installed at version 1.3.2 or earlier. The CVSS vector indicates exploitation requires high privileges, reducing broad internet-scale risk but making administrator-account compromise more concerning.
Exploitation context
The provided sources do not describe public exploit code, active exploitation, or detailed attack prerequisites beyond the CVSS vector. KEV status is false. Treat this as a plugin-specific hardening and patch-management item, not confirmed active campaign activity.
Researcher notes
The source bundle has limited remediation detail. It identifies the vulnerability class, affected plugin, version range, CVSS vector, and Patchstack entry, but not a patched version or exploit details. Avoid assuming exploitability beyond authenticated high-privilege SSRF until vendor details are available.
Mitigation direction
Inventory WordPress sites for the Solace Extra plugin and version.
Check vendor, WordPress plugin, or Patchstack guidance for a fixed release.
Update the plugin if a vendor-supported fixed version is available.
Disable or remove Solace Extra where it is not business-critical.
Limit high-privilege WordPress accounts to trusted administrators only.
Validation and detection
Confirm whether Solace Extra is installed on each WordPress site.
Record installed plugin versions and flag versions <=1.3.2.
Review administrator account access and recent privileged activity.
Check web server logs for unusual outbound-request-related errors or patterns.
Track CVE and Patchstack pages for updated remediation details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.