CVE-2025-12367

SiteSEO – SEO Simplified <= 1.3.1 - Missing Authorization to Authenticated (Author+) Plugin Settings Update

Strategic Overview

Status
Patched in 1.3.2
Affected Version
<= 1.3.1
CVSS
4.3Medium
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2025-12367
View all SiteSEO – SEO Simplified vulnerabilities

At a glance

CVE-2025-12367 is a medium-severity Improper Authorization vulnerability in the SiteSEO WordPress plugin, affecting versions <= 1.3.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 1.3.2; sites on affected versions should update now. Disclosed October 2025, reported by Athiwat Tiprasaharn (Jitlada).

Vulnerability Overview

The SiteSEO – SEO Simplified plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.3.1. 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 Author-level access and above, to enable or disable arbitrary SiteSEO features that they should not have access to.

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

Reaching this weakness in SiteSEO <= 1.3.1 takes an account at Author 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 SiteSEO the fix is 1.3.2: builds <= 1.3.1 are affected, anything from 1.3.2 onward is not.

Remediation

Update to version 1.3.2, 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: SiteSEO 1.3.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C