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.
Security readout for executives and security teams
Plain-English summary
ProSolution WP Client through version 2.0.10 may let an unauthenticated internet visitor place a potentially executable file on a WordPress server. Successful abuse could enable complete website and server compromise, including data theft, content manipulation, and service disruption. Risk is greatest where a public page renders the plugin’s job portal shortcode.
Executive priority
Treat this as an emergency exposure review for internet-facing WordPress systems. Immediately inventory affected installations, isolate or disable exposed instances, and investigate for suspicious uploads. Restore normal operation only after applying vendor-confirmed remediation and validating that writable directories cannot execute uploaded content.
Technical view
The upload handler trusts an attacker-controlled Content-Disposition filename that can replace the allow-listed multipart filename. The extension check occurs after writing the file and reportedly fails to remove it. A nonce exposed through wp_localize_script on job portal pages allows unauthenticated access to the handler. Whether an uploaded file executes depends on server and upload-directory configuration.
Likely exposure
Prioritize internet-facing WordPress sites running ProSolution WP Client 2.0.10 or earlier, especially sites publishing the job portal shortcode. Exposure may be reduced where the plugin is absent, the shortcode is not rendered publicly, or uploaded files cannot execute. The supplied affected-version metadata is internally inconsistent, so verify installed versions directly.
Exploitation context
The supplied sources support unauthenticated arbitrary file upload and possible remote code execution. They do not establish observed exploitation in the wild, and the bundle states that CVE-2026-16098 is not in KEV. Absence from KEV does not prove that exploitation is not occurring.
Researcher notes
CWE-434 and CVSS 3.1 score 9.8 fit the described unauthenticated upload path. The bundle’s title and description say versions through 2.0.10 are affected, but its structured affected entry lists version “0” with default status unaffected. Included source-code links target 2.0.6, and no explicit fixed version is named. Avoid interpreting the referenced changeset alone as proof of complete remediation.
Mitigation direction
Identify and prioritize all installations running ProSolution WP Client 2.0.10 or earlier.
Check current vendor guidance and install a vendor-confirmed fixed release when available.
Disable or remove the affected plugin until a confirmed remediation is applied.
Restrict public access to pages rendering the job portal shortcode during remediation.
Prevent executable code from running in upload directories as defense in depth.
Validation and detection
Confirm the installed plugin version from trusted WordPress inventory or filesystem records.
Identify public pages that render the ProSolution job portal shortcode.
Review upload locations for unexpected scripts or recently created executable file types.
Review web and application logs for unusual requests to the plugin’s upload functionality.
Verify server configuration prevents code execution from writable upload directories.
After remediation, confirm the affected plugin version or functionality is no longer present.
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-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell 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.
1CVSS vectors
4Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
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-434 · source CWE mapping
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.