ERP: Complete HR, Accounting & CRM Suite Built for WooCommerce <= 1.17.6 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Company Location Creation via wp_ajax_erp-company-location AJAX Handler
The ERP: Complete HR, Accounting & CRM Suite Built for WooCommerce plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.17.6. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to create arbitrary company locations in the ERP database.
Browse WordPress security risksQuick answer
ERP: Complete HR, Accounting & CRM Suite Built 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
- up to and including 1.17.6
Fixed versions
- 1.17.7
How to fix it
ERP: Complete HR, Accounting & CRM Suite Built for WooCommerce is affected by CVE-2026-15349, a missing authorization flaw in the company location AJAX handler. A subscriber can create unauthorized company locations and change ERP data. Update ERP: Complete HR, Accounting & CRM Suite Built for WooCommerce to 1.17.7 or a newer vendor-supported patched release. Prioritize exposed production systems and accounts that can reach the affected feature.
- Inventory every ERP: Complete HR, Accounting & CRM Suite Built for WooCommerce deployment, version, exposed endpoint, environment, and owner.
- Confirm the installed release is not an affected version up to and including 1.17.6.
- Update ERP: Complete HR, Accounting & CRM Suite Built for WooCommerce to 1.17.7 or a newer vendor-supported patched release.
- Until the update is complete, disable WP ERP or block subscriber access to the erp-company-location handler.
- Review subscriber AJAX calls, unexpected company-location rows, and changes in related ERP workflows.
- Remove unauthorized locations, correct downstream ERP records, and revoke accounts that abused the handler.
- Clear WordPress, object, page, CDN, and browser caches, then update the asset inventory and close any temporary controls only after validation.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm ERP: Complete HR, Accounting & CRM Suite Built for WooCommerce is on the patched version or mitigation stated above and record the exact deployed version.
- Confirm a subscriber cannot create or change a company location without the required capability.
- Confirm the affected WordPress REST, AJAX, form, shortcode, upload, export, or admin feature is available only to the roles and requests that need it.
- Review logs after remediation for continued exploit attempts or signs that the issue was used before the fix.
- Rerun the relevant dependency, platform, vendor, or Fixnx security check and document the result, affected assets, change record, and cleanup evidence for CVE-2026-15349.
Related categories
Related security risks
More published guidance from the same primary category.
Payment Plugins for Stripe WooCommerce <= 4.0.7 - Missing Authorization to Unauthenticated Arbitrary Order Status Modification via Empty Webhook Secret
Updated July 24, 2026
highCVE-2026-65500 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability
Updated July 24, 2026
mediumParticipants Database <= 2.7.8.3 - Missing Authorization to Unauthenticated Arbitrary Record Update / Sensitive Information Exposure via 'id' Parameter
Updated July 24, 2026
Trusted references
FAQ
What is affected by CVE-2026-15349?
ERP: Complete HR, Accounting & CRM Suite Built for WooCommerce versions listed as affected should be reviewed: up to and including 1.17.6.
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.
