Autopay
platnosci-online-blue-media · plugin
Known security vulnerabilities for Autopay. Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
4 exploitable without logging in · latest Sep 17, 2026
Before you install
Use with care
- 4 records needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 5.1.0 · last updated Oct 26, 2026 · 3K+ installs
wordpress.org status checked on Nov 8, 2026
Vulnerabilities
- High 8.8
CVE-2026-14293unauthenticated · needs a click→ 5.0.1
Autopay / Blue Media for WooCommerce < 5.0.1 - Unauthenticated Stored XSS via CSS Editor
- High 7.2
CVE-2026-15002unauthenticated≤ 5.0.0
Autopay <= 5.0.0 - Unauthenticated Stored Cross-Site Scripting via 'bm_woocommerce_css_editor_content' Parameter
- High 7.1
CVE-2026-73338unauthenticated · needs a click≤ 5.0.0
WordPress Autopay plugin <= 5.0.0 - Cross Site Scripting (XSS) vulnerability
- Medium 6.5
CVE-2026-90923unauthenticated→ 5.0.1
Autopay < 5.0.1 - Unauthenticated Cross-Customer Order Payment Parameter Disclosure and Deletion
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.