Rankology SEO and Analytics Tool <= 2.0 - Incorrect Authorization to Authenticated (Editor+) Header & Footer Code Creation
Strategic Overview
- Status
- Patched in 2.5
- Affected Plugin
- Rankology SEO and Analytics Tool
- Affected Version
<= 2.0- CVSS
- 2.7Low
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE-2025-12958
At a glance
CVE-2025-12958 is a low-severity Improper Authorization vulnerability in the Rankology SEO and Analytics Tool WordPress plugin, affecting versions <= 2.0. It carries a CVSS score of 2.7 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 2.5; sites on affected versions should update now. Disclosed January 2026, reported by SangNQ29.
Vulnerability Overview
The Rankology SEO and Analytics Tool plugin for WordPress is vulnerable to unauthorized modification of data due to an incorrect capability check on the 'rankology_code_block' page in all versions up to, and including, 2.0. This makes it possible for authenticated attackers, with Editor-level access and above, to add header and footer code blocks.
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-285: Improper Authorization
Rankology SEO and Analytics Tool <= 2.0 carries this weakness at rankology_code_block, and reaching it takes an account at Editor level or above. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.
A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For Rankology SEO and Analytics Tool the fix is 2.5: builds <= 2.0 are affected, anything from 2.5 onward is not.
Remediation
Update to version 2.5, 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: Rankology SEO and Analytics Tool 2.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C