Skip to main content

ProSolution WP Client CVE-2026-16098

| EUVDEUVD-2026-59855 CRITICAL
Unrestricted Upload of File with Dangerous Type (CWE-434)
2026-08-16 Wordfence GHSA-7vxm-f6w4-qrp3
9.8
CVSS 3.1 · Vendor: Wordfence
Share

Severity by source

Vendor (Wordfence) PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
9.8 CRITICAL

Nonce is publicly leaked so PR:N holds; remote, no interaction, and file-upload-to-RCE yields full C:H/I:H/A:H on the host, matching the vendor score.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Analysis Generated
Aug 16, 2026 - 05:02 vuln.today
CVE Published
Aug 16, 2026 - 04:24 cve.org
CRITICAL 9.8

DescriptionCVE.org

The ProSolution WP Client plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 2.0.10 via the proSol_handleFileUpload function. This is due to missing validation of the attacker-controlled Content-Disposition header filename, which overrides the allow-listed multipart filename before the file is saved, and a post-save extension check that fails to delete the already-written file. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible. The nonce required to reach the upload handler is publicly exposed via wp_localize_script on any front-end page rendering the job portal shortcode, allowing unauthenticated visitors to obtain a valid nonce and bypass that gating check entirely.

AnalysisAI

Unauthenticated arbitrary file upload leading to remote code execution affects the ProSolution WP Client WordPress plugin in all versions through 2.0.10, via the proSol_handleFileUpload function. The handler trusts the attacker-supplied Content-Disposition filename over the validated multipart filename and, critically, fails to delete files that its post-save extension check rejects, so a malicious PHP file remains on disk and executable. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Load public page with job-portal shortcode
Delivery
Scrape leaked wp_localize_script nonce
Exploit
POST upload with malicious Content-Disposition filename
Execution
File written before failed extension check
Persist
Request uploaded webshell directly
Impact
Execute arbitrary code on server

Vulnerability AssessmentAI

Exploitation Exploitation requires that the target WordPress site render the plugin's job-portal shortcode on at least one publicly reachable front-end page - that shortcode is the specific feature that both exposes the reachable proSol_handleFileUpload handler and leaks a valid nonce via wp_localize_script, so sites that never place the shortcode on a public page are not exposed. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment This is a genuine high-priority issue, not a paper-tiger high CVSS. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An unauthenticated attacker loads a public site page containing the job-portal shortcode, scrapes the valid nonce embedded by wp_localize_script, then sends a crafted multipart upload whose Content-Disposition filename ends in .php while the multipart filename appears benign. The plugin writes the PHP payload to disk before its extension check rejects it - but never deletes it - leaving a web-accessible webshell the attacker requests directly to run arbitrary code. …
Remediation Update to a fixed release above 2.0.10 as soon as the vendor publishes one; the input data does not include a confirmed fixed version, so no vendor-released patch version is independently confirmed at time of analysis - monitor the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/3c4a7aef-09ec-4d17-87d6-f507d64e0afa?source=cve) and the plugin changeset (https://plugins.trac.wordpress.org/changeset?reponame=&old=3644463%40prosolution-wp-client&new=3644463%40prosolution-wp-client) for the patched tag. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Immediately audit all WordPress installations for the ProSolution WP Client plugin and deactivate it at the administration panel to prevent exploitation; if the plugin's functionality is critical, begin identifying replacement solutions. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-16098 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy