Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-103525 Overview
CVE-2026-103525 is an Insecure Direct Object Reference (IDOR) vulnerability in the FluentCart eCommerce plugin for WordPress, affecting all versions up to and including 1.7.0. The flaw resides in an unauthenticated AJAX endpoint that pairs order_id with billing_address_id or shipping_address_id without validating ownership. Attackers can enumerate sequential AUTO_INCREMENT identifiers to exfiltrate stored customer personally identifiable information (PII). Exposed fields include street address, city, state, postcode, phone number, company name, VAT number, and legal registration ID. The weakness maps to CWE-639: Authorization Bypass Through User-Controlled Key.
Critical Impact
Unauthenticated remote attackers can harvest billing and shipping PII of every FluentCart customer by iterating order and address ID pairs against a weakly rate-limited endpoint.
Affected Products
- FluentCart plugin for WordPress — all versions up to and including 1.7.0
- api/Checkout/CheckoutApi.php endpoints handling order and address lookups
- app/Hooks/Cart/WebCheckoutHandler.php web checkout handler
Discovery Timeline
- 2026-10-16 - CVE-2026-103525 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-103525
Vulnerability Analysis
The vulnerability affects the FluentCart checkout API, specifically the handlers that resolve billing and shipping addresses for an order. The endpoint accepts both an order_id and an address_id from the request body and uses an id-equality check as its only authorization guard. Because the attacker supplies both identifiers, the comparison is trivially satisfied with any valid pair harvested from sequential enumeration.
The endpoint is reachable without authentication. Its only abuse control is a soft rate limit of five requests per 60 seconds, which does not prevent sustained enumeration over hours or distributed scraping from multiple source addresses.
Root Cause
The root cause is missing ownership validation on a user-controlled key [CWE-639]. The code does not verify that the submitted billing_address_id or shipping_address_id belongs to the authenticated session or to the customer who placed the referenced order. Instead, it only confirms that the two IDs reference each other, a condition the attacker fully controls.
Attack Vector
An unauthenticated attacker sends crafted AJAX requests to the FluentCart checkout endpoint, iterating order_id values against candidate address_id values. Successful pairs return the stored address record in the response. Because order and address IDs are issued by MySQL AUTO_INCREMENT, the attacker can estimate the valid range and enumerate the full customer base. See the vendor source references in CheckoutApi.php line 124, line 338, and line 369.
The vulnerability affects confidentiality only; no integrity or availability impact is reported. No public proof-of-concept exploit is listed, and the vulnerability is not present in the CISA Known Exploited Vulnerabilities catalog.
Detection Methods for CVE-2026-103525
Indicators of Compromise
- Repeated unauthenticated POST requests to FluentCart checkout AJAX endpoints with incrementing order_id or address_id parameters.
- Request volumes approaching the five-per-60-second rate limit from one or more source IP addresses over extended time windows.
- Response bodies containing billing or shipping address fields returned to clients that never completed a checkout session.
Detection Strategies
- Inspect web server access logs for sequential numeric enumeration patterns against FluentCart endpoints referenced in api/Checkout/CheckoutApi.php.
- Correlate unauthenticated requests to checkout AJAX actions with unusually high response payload sizes containing PII fields.
- Deploy a Web Application Firewall (WAF) rule to flag parameter pairs where order_id and address_id increment linearly across short time intervals.
Monitoring Recommendations
- Enable verbose logging on WordPress AJAX endpoints and ingest the logs into a SIEM for enumeration pattern analysis.
- Alert on bursts of requests from a single source hitting the rate-limit threshold of five per 60 seconds.
- Monitor for distributed requests across multiple IPs targeting the same WordPress site with sequential ID patterns.
How to Mitigate CVE-2026-103525
Immediate Actions Required
- Update FluentCart to a version later than 1.7.0 that includes the fix tracked in changeset 3734886.
- Audit WordPress access logs for prior unauthenticated enumeration of FluentCart checkout endpoints and notify affected customers if PII was returned.
- Deploy WAF rules to block or heavily throttle unauthenticated requests to the vulnerable AJAX actions until patching is complete.
Patch Information
The vendor fix is published as changeset 3734886 in the WordPress plugin repository. Review the Wordfence advisory 8375a8f4 for the fixed version string and confirm installations are upgraded accordingly.
Workarounds
- Restrict access to the FluentCart checkout AJAX endpoints at the WAF or reverse proxy layer, allowing only authenticated session traffic.
- Enforce a stricter rate limit than the plugin default of five requests per 60 seconds for unauthenticated clients.
- Temporarily disable the FluentCart plugin on production sites that cannot upgrade immediately, especially where stored customer PII volume is high.
# Example nginx rate-limit and allow-list snippet for FluentCart AJAX
limit_req_zone $binary_remote_addr zone=fcart:10m rate=1r/m;
location ~* /wp-admin/admin-ajax\.php {
limit_req zone=fcart burst=2 nodelay;
# Block known enumeration user-agents
if ($http_user_agent ~* "(curl|wget|python-requests)") { return 403; }
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

