Skip to main content
VulnerabilityPublished Updated

CVE-2026-14524: ProSolution WP Client · Path Traversal

Affects ProSolution WP ClientSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical.

Data as of 14 Nov 2026, 20:44 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
prosolutionProSolution WP ClientAffected
  • <=2.0.8
Fixed in–

AI-suggested

Until an official fix is available, restrict access to the affected plugin and monitor for suspicious activity involving the proSol_fileUploadModalProcess and proSol_fileDeleteProcess handlers. Avoid exposing frontend nonces publicly if possible.

Description

The ProSolution WP Client plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the proSol_fileDeleteProcess function in all versions up to, and including, 2.0.8. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). An attacker must first call the proSol_fileUploadModalProcess handler to poison their own session with a path-traversal key, then call proSol_fileDeleteProcess with that key as the filename parameter; both steps require only the publicly exposed frontend nonce.

References

Community reviews

Loading reviews…