Vulnerabilities and security researches forprosolution-wp-client prosolution-wp-client

Apr 14, 2026

CVE, Research URL: CVE-2026-2942
Home page URL: Security reports for ProSolution WP Client
Application: ProSolution WP Client
Date: Apr 09, 2026
Research Description: The ProSolution WP Client plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'proSol_fileUploadProcess' function in all versions up to, and including, 1.9.9. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
Affected versions: max 2.0.0.
Status: vulnerable

May 23, 2026

CVE, Research URL: CVE-2026-6555
Home page URL: Security reports for ProSolution WP Client
Application: ProSolution WP Client
Date: May 20, 2026
Research Description: The ProSolution WP Client plugin for WordPress is vulnerable to Arbitrary File Upload in versions up to, and including, 2.0.0. This is due to an array validation mismatch where only the first file in the upload array undergoes extension and MIME type validation, while all files are processed and uploaded to a web-accessible directory. This makes it possible for unauthenticated attackers to upload malicious PHP files and achieve remote code execution by sending a valid first file followed by a malicious file.
Affected versions: max 2.0.0.
Status: vulnerable

Aug 12, 2026

CVE, Research URL: CVE-2026-19053
Home page URL: Security reports for ProSolution WP Client
Application: ProSolution WP Client
Date: Aug 10, 2026
Research Description: The ProSolution WP Client WordPress plugin before 2.0.6 does not sanitise and escape a parameter before using it in a SQL statement reachable by unauthenticated visitors, leading to a blind SQL injection.
Affected versions: max 2.0.6.
Status: vulnerable

CVE, Research URL: CVE-2026-19049
Home page URL: Security reports for ProSolution WP Client
Application: ProSolution WP Client
Date: Aug 10, 2026
Research Description: The ProSolution WP Client WordPress plugin before 2.0.9 does not sanitise a cookie value before using it in SQL queries, and processes that cookie on every request without any authentication or capability check, allowing unauthenticated users to read arbitrary data from the database and to delete the records the ProSolution WP Client WordPress plugin before 2.0.9 stores.
Affected versions: max 2.0.9.
Status: vulnerable

Aug 18, 2026

CVE, Research URL: CVE-2026-16098
Home page URL: Security reports for ProSolution WP Client
Application: ProSolution WP Client
Date: Aug 16, 2026
Research Description: 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.
Affected versions: max 2.0.11.
Status: vulnerable

CVE, Research URL: CVE-2026-14524
Home page URL: Security reports for ProSolution WP Client
Application: ProSolution WP Client
Date: Aug 16, 2026
Research 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.
Affected versions: max 2.0.9.
Status: vulnerable