CVE-2025-1313

Nokri - Job Board WordPress Theme <= 1.6.3 - Authenticated (Subscriber+) Privilege Escalation via Account Takeover

2025-07-11 16:27
Tonn

Strategic Overview

Status
Patched in 1.6.4
Affected Version
<= 1.6.3
CVSS
8.8High
Weakness type
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
CVE
CVE-2025-1313
View all Nokri – Job Board WordPress Theme vulnerabilities

At a glance

CVE-2025-1313 is a high-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Nokri WordPress theme, affecting versions <= 1.6.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.6.4; sites on affected versions should update now. Disclosed July 2025, reported by Tonn.

Vulnerability Overview

The Nokri - Job Board WordPress Theme theme for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.6.3. This is due to the plugin not properly validating a user's identity prior to updating their details like email address. This makes it possible for authenticated attackers, with Subscriber-level access and above, to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-288: Authentication Bypass Using an Alternate Path or Channel

Reaching this weakness in Nokri <= 1.6.3 takes an account at Subscriber level or above. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.

The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For Nokri the fix is 1.6.4: builds <= 1.6.3 are affected, anything from 1.6.4 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

Related records

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