HomeWordPress vulnerabilitiesWCPOS
WCPOS vulnerabilities
WCPOS has 2 known vulnerabilities in this database. The most recent published record is dated 16 Aug 2026.
- Known vulnerabilities
- 2
- Active installs
- 5,000+
- Latest version
- 1.10.20
- Last updated
- 23 Sep 2026
- Most recent
- 16 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2026-17581 | High 7.2 | Up to 1.9.14 | Fixed in a later version (latest 1.10.20) | 16 Aug 2026 |
| Path traversal CVE-2026-16078 | Medium 6.5 | Up to 1.9.8 | Fixed in a later version (latest 1.10.20) | 23 Jul 2026 |
Read the published descriptions
- CVE-2026-17581, 16 Aug 2026
- The WCPOS - Point of Sale (POS) plugin for WooCommerce plugin for WordPress is vulnerable to Code Injection via the 'thermal' Template Engine in all versions up to, and including, 1.9.14 due to the Receipt_Renderer_Factory dispatching templates with the 'thermal' engine to the Legacy_Php_Renderer instead of a safe thermal-specific renderer. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to inject arbitrary PHP code into a template post that is subsequently written to a temporary file and executed via PHP's include(), resulting in remote code execution on the server. This requires the attacker to have Shop Manager-level access or above, as the template save path enforces a wcpos_template_settings nonce and the manage_woocommerce_pos capability check. CVE record
- CVE-2026-16078, 23 Jul 2026
- The WCPOS - Point of Sale (POS) plugin for WooCommerce plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.9.8 via the 'type' parameter parameter. This makes it possible for authenticated attackers, with shop manager-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information. Successful exploitation requires supplying context=edit in the request, which bypasses the content-stripping logic in prepare_item_for_response() and returns the traversed file verbatim in the REST API response. CVE record
What to do if you run WCPOS
If you run WCPOS, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WCPOS vulnerabilities
Free. We email you when a new vulnerability is published for WCPOS, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.