CVE-2026-129327: Apaczka.pl WooCommerce <= 1.4.8 - Unauthenticated Stored Cross-Site Scripting via '_apaczka' Parameter via Guest Checkout
The Apaczka.pl WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'apaczka[<id>][errormessages] (and sibling subkeys inside apaczka[])' parameter in all versions up to, and including, 1.4.8 due to insufficient input sanitization and 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. This is exploitable during WooCommerce classic guest checkout because WooCommerce's legacy order storage fires the savepost action with the checkout $POST still populated, giving unauthenticated attackers a direct write path to order post meta without an authenticated session.
Affected Software
Event History
Frequently Asked Questions
Which sites are exposed to unauthenticated exploitation?
Sites using Apaczka.pl WooCommerce version 1.4.8 or earlier may be exposed when WooCommerce classic guest checkout is available and legacy order storage is in use. An attacker does not need an authenticated WordPress or WooCommerce session.
What must an attacker do to exploit the issue?
The attacker needs to submit crafted _apaczka array parameters, including error_messages or related subkeys, through a classic guest checkout. The vulnerable legacy order-saving path can then write the supplied content into order post meta.
When does the injected script execute?
The payload is stored and executes when a user accesses a page that renders the injected content. The issue can therefore affect users who later view the relevant order-related page, rather than only the attacker during checkout.
What configuration detail is important when assessing impact?
The described unauthenticated write path depends on WooCommerce classic guest checkout and legacy order storage, where the save_post action runs while checkout POST data remains populated. The supplied data does not establish whether other checkout or order-storage configurations are affected.