HomeWordPress vulnerabilitiesAutopay
Autopay vulnerabilities
Autopay has 3 known vulnerabilities in this database. The most recent published record is dated 17 Sep 2026.
- Known vulnerabilities
- 3
- Active installs
- 3,000+
- Latest version
- 5.0.5
- Last updated
- 28 Sep 2026
- Most recent
- 17 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-90923 | Medium 6.5 | Before 5.0.1 | Fixed in 5.0.1 | 17 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-15002 | High 7.2 | Up to 5.0.0 | Fixed in a later version (latest 5.0.5) | 16 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-14293 | High 8.8 | Before 5.0.1 | Fixed in 5.0.1 | 10 Aug 2026 |
Read the published descriptions
- CVE-2026-90923, 17 Sep 2026
- The Autopay WordPress plugin before 5.0.1 does not enforce the signature on one of its payment callbacks, allowing unauthenticated users to disclose and delete the stored payment parameters of other customers' orders. CVE record
- CVE-2026-15002, 16 Aug 2026
- The Platnosci Online Blue Media (Autopay) plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 5.0.0 via the 'bm_woocommerce_css_editor_content' POST parameter. This is due to the Css_Editor::handle_save() method being wired to the WordPress 'init' hook by Settings_Manager::init_once() with no capability check, no nonce verification, and no sanitization on the input - the raw $_POST value is written to the 'woocommerce_bluemedia_settings' option via update_option(), then later echoed directly inside a <style> block on the WooCommerce checkout page by Css_Frontend::print_to_wp_head() with no output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page (the checkout page). CVE record
- CVE-2026-14293, 10 Aug 2026
- The Autopay WordPress plugin before 5.0.1 does not perform any capability or nonce check before saving a styling option from a public request, and does not escape that value when it is later output on the checkout page, allowing unauthenticated attackers to store JavaScript that executes in the browser of any user, including administrators, who loads the checkout page. CVE record
What to do if you run Autopay
If you run Autopay, 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 Autopay vulnerabilities
Free. We email you when a new vulnerability is published for Autopay, 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.