HomeWordPress vulnerabilitiesInPost PL
InPost PL vulnerabilities
InPost PL has 3 known vulnerabilities in this database. The most recent published record is dated 30 Sep 2026.
- Known vulnerabilities
- 3
- Active installs
- 10,000+
- Latest version
- 1.9.8
- Last updated
- 23 Sep 2026
- Most recent
- 30 Sep 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 |
|---|---|---|---|---|
| Broken access control CVE-2026-93580 | Medium 5.3 | Before 1.9.8 | Fixed in 1.9.8 | 7 d ago |
| Security weakness CVE-2026-9702 | High 7.5 | Before 1.9.1 | Fixed in 1.9.1 | 25 Jun 2026 |
| Broken access control CVE-2024-6500 | Critical 10.0 | Up to 1.4.0 | Fixed in a later version (latest 1.9.8) | 17 Aug 2024 |
Read the published descriptions
- CVE-2026-93580, 30 Sep 2026
- The InPost PL WordPress plugin before 1.9.8 does not verify the authenticity of incoming shipment webhook requests, relying only on a non-secret identifier and an IP check that is not enforced, allowing unauthenticated attackers who know a target order's parcel tracking number to forge its shipment status and prematurely mark the order completed. CVE record
- CVE-2026-9702, 25 Jun 2026
- The InPost PL WordPress plugin before 1.9.1 does not verify that the request originates from the legitimate buyer before allowing the WooCommerce order parcel-locker destination to be updated, allowing unauthenticated attackers to silently redirect the shipping destination of any pending or processing order on the site. CVE record
- CVE-2024-6500, 17 Aug 2024
- The InPost for WooCommerce plugin and InPost PL plugin for WordPress are vulnerable to unauthorized access and deletion of data due to a missing capability check on the 'parse_request' function in all versions up to, and including, 1.4.0 (for InPost for WooCommerce) as well as 1.4.4 (for InPost PL). This makes it possible for unauthenticated attackers to read and delete arbitrary files on Windows servers. On Linux servers, only files within the WordPress install will be deleted, but all files can be read. CVE record
What to do if you run InPost PL
If you run InPost PL, 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 InPost PL vulnerabilities
Free. We email you when a new vulnerability is published for InPost PL, 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.