SmartCrawl SEO checker, analyzer & optimizer <= 3.16.4 - Authenticated (Contributor+) Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 3.17.1
- Affected Plugin
- SmartCrawl SEO checker, analyzer & optimizer
- Affected Version
<= 3.16.4- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-110901
At a glance
CVE-2026-110901 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the SmartCrawl SEO checker, analyzer & optimizer WordPress plugin, affecting versions <= 3.16.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.17.1; sites on affected versions should update now. Disclosed October 2026, reported by AndrewN.
Vulnerability Overview
The SmartCrawl SEO checker, analyzer & optimizer plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.16.4. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to perform an unauthorized action.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in SmartCrawl SEO checker, analyzer & optimizer <= 3.16.4 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For SmartCrawl SEO checker, analyzer & optimizer the fix is 3.17.1: builds <= 3.16.4 are affected, anything from 3.17.1 onward is not.
Remediation
Update to version 3.17.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: SmartCrawl SEO checker, analyzer & optimizer 3.17.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in SmartCrawl SEO checker, analyzer & optimizer
- 5.3CVE-2024-6556: SmartCrawl WordPress SEO checker Full Path Disclosure
CVE-2024-6556 - 5.3CVE-2024-3287: SmartCrawl WordPress SEO checker Missing Authorization
CVE-2024-3287 - 5.3CVE-2023-5949: Simple Social… Password Protected Post Disclosure
CVE-2023-5949 - 4.3CVE-2026-16979: SmartCrawl SEO checker Missing Authorization
CVE-2026-16979 - 4.3CVE-2025-62048: SmartCrawl <= 3.14.3 Missing Authorization
CVE-2025-62048 - 4.3CVE-2025-11163: SmartCrawl SEO checker Plugin Settings Update
CVE-2025-11163
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C