Summary
CVE-2026-18550 is a critical privilege escalation vulnerability in the Nokri – Job Board WordPress Theme (developed by scriptsbundle) affecting all versions up to and including 1.6.6. The flaw resides in the theme’s password reset logic and allows a completely unauthenticated attacker to take over any user account, including administrators. It carries a CVSS v3.1 base score of 9.8 (Critical).
Technical details
- Root cause: the
nokri_reset_password()function does not properly validate the password reset token supplied in the request against the token stored in thesb_password_forget_tokenuser meta value. - Trigger condition: when a user has never requested a password reset (or the stored token is empty/unset), an attacker can submit an empty token value, which matches the empty/unset stored value and passes validation.
- Attack vector: remote, over the network, via the theme’s password reset request handling — no authentication or user interaction required.
- Impact: successful exploitation lets an attacker set a new password for any account, including administrator accounts, resulting in full account takeover and complete loss of confidentiality, integrity, and availability for the affected site.
Affected software
- Nokri – Job Board WordPress Theme (vendor: scriptsbundle), all versions up to and including 1.6.6.
Severity
CVSS v3.1 Base Score: 9.8 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: No patched version has been publicly confirmed at the time of writing. Site owners should monitor the vendor (scriptsbundle) for a fixed release of the Nokri theme and update immediately once available.
- If no patch is available: disable or restrict access to the theme’s password reset functionality, monitor for suspicious password reset requests (particularly those with empty or missing tokens), enforce multi-factor authentication for administrator accounts, and consider taking the affected reset endpoint offline via a web application firewall rule until a fix is released.
How IONIX identifies potentially affected assets
IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Raw response body:
/wp-content/themes/nokri/

