AR for WooCommerce <= 8.40 - Unauthenticated Path Traversal to Arbitrary File Read via 'file' Parameter
The AR for WooCommerce plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 8.40 via the 'file' parameter parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. The three intended access controls all fail: valid nonces are freely minted by unauthenticated callers via the nopriv ar_get_fresh_nonce and ar_process_user_image AJAX handlers; the AES-256-CBC encryption key is derived from get_option('ar_licence_key'), which returns false on default free installations and yields a predictable key attackers can use to encrypt their own path payloads; and the Referer check is trivially bypassed because the Referer header is attacker-controlled.
Quick answer
AR for WooCommerce should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-8.40
Fixed versions
- 8.41
How to fix it
AR for WooCommerce is affected by CVE-2026-14352, unauthenticated path traversal that can read arbitrary files through the file parameter in *-8.40. Prioritize production WordPress sites where the plugin or theme is enabled, especially if unauthenticated users can reach the vulnerable workflow. The recommended remediation is to update to version 8.41 or a newer vendor-supported patched release. If immediate patching is not possible, reduce exposure, restrict access to the vulnerable feature, and monitor logs until the vendor-supported fix is in place.
- Inventory every WordPress site that uses AR for WooCommerce, including production, staging, multisite, customer, and managed environments.
- Confirm the installed plugin or theme version and compare it with the affected range: *-8.40.
- Apply the remediation: update to version 8.41 or a newer vendor-supported patched release.
- If the update cannot be applied immediately, disable AR for WooCommerce or restrict the affected admin, REST, AJAX, shortcode, upload, booking, ecommerce, profile, form, gallery, or theme workflow to trusted administrators only.
- Review application, web server, WordPress security plugin, WAF, authentication, and administrator activity logs for attempts related to CVE-2026-14352.
- Remove suspicious stored content, uploaded files, generated logs, injected scripts, unexpected appointments/orders/posts, or altered configuration created through the affected workflow.
- Clear application, object, page, CDN, and browser caches after remediation so stale vulnerable responses or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm AR for WooCommerce is no longer running *-8.40 and record the patched or mitigated version in the remediation ticket.
- Verify unauthenticated users can no longer trigger the affected action or access data outside their intended permissions.
- Review logs before and after the fix for exploitation attempts, suspicious role activity, unexpected content changes, file reads, SQL errors, or unauthorized data access.
- Rerun a Fixnx scan and any relevant plugin, WAF, or manual regression checks to confirm public exposure is reduced.
- Document the advisory, affected assets, remediation action, verification evidence, and any cleanup or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-14352?
AR for WooCommerce versions listed as affected should be reviewed: *-8.40.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.