CVE-2026-19050

ProSolution WP Client <= 2.0.8 - Authenticated (Subscriber+) Server-Side Request Forgery

2026-08-10 00:00
Nir Yehoshua

Strategic Overview

Status
Patched in 2.0.9
Affected Plugin
ProSolution WP Client
Affected Version
<= 2.0.8
CVSS
6.4Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2026-19050
View all ProSolution WP Client vulnerabilities

At a glance

CVE-2026-19050 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the ProSolution WP Client WordPress plugin, affecting versions <= 2.0.8. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.9; sites on affected versions should update now. Disclosed August 2026, reported by Nir Yehoshua.

Vulnerability Overview

The ProSolution WP Client plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 2.0.8. This is due to a missing capability check on the proSol_url_validate() AJAX handler allowing any authenticated user to trigger outbound requests to arbitrary URLs, combined with a lack of SSRF validation on the urlval parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to make web requests to arbitrary locations originating from the web application, including internal network resources and cloud metadata endpoints.

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)

ProSolution WP Client <= 2.0.8 carries this weakness at proSol_url_validate(), and reaching it takes an account at Subscriber 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 ProSolution WP Client the fix is 2.0.9: builds <= 2.0.8 are affected, anything from 2.0.9 onward is not.

Remediation

Update to version 2.0.9, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber 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: ProSolution WP Client 2.0.9 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-19050https://www.wordfence.com/threat-intel/vulnerabilities/id/b3e20ad5-6279-4585-924f-c7289e7dc753https://nvd.nist.gov/vuln/detail/CVE-2026-19050

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C