Security readout for executives and security teams
Plain-English summary
Nokri Job Board WordPress Theme versions through 1.6.6 may let an unauthenticated attacker reset any user’s password, including an administrator’s. Successful abuse could give an attacker complete control of the website, its data, and administrative functions.
Executive priority
Treat this as an immediate remediation priority for internet-facing Nokri deployments. Administrator takeover could produce site compromise, data exposure, malicious modifications, and service disruption. Establish ownership and exposure today, then remediate or isolate affected sites.
Technical view
The nokri_reset_password() function insufficiently validates attacker-supplied reset tokens. An empty token can match an empty or unset sb_password_forget_token user-meta value, allowing password reset and account takeover without authentication. The supplied CVSS 3.1 score is 9.8.
Likely exposure
Internet-accessible WordPress sites running Nokri version 1.6.6 or earlier are potentially exposed. Risk is greatest where administrator accounts have an empty or unset password-reset token value. The source bundle provides no reliable affected CPE inventory.
Exploitation context
The issue requires no authentication, user interaction, or elevated access and can lead directly to administrator takeover. The bundle does not report confirmed exploitation, and the CVE is not identified as being in CISA KEV. Exploitation status therefore remains unconfirmed.
Researcher notes
The supplied affected-version record contains an anomalous versions value of "0" with defaultStatus "unaffected," while the title and description state all versions through 1.6.6 are vulnerable. Validate version boundaries and any fixed release against current vendor or Wordfence guidance. No exploit procedure or confirmed exploitation evidence is included.
Mitigation direction
- Identify all WordPress sites using Nokri and record their installed versions.
- Check Wordfence and Nokri vendor guidance for a confirmed fixed release or mitigation.
- Apply the vendor-supported correction promptly when confirmed, prioritizing internet-facing sites.
- If no correction is available, restrict public access or disable the affected theme where operationally feasible.
- Reset potentially compromised administrator credentials and invalidate active sessions after remediation.
Validation and detection
- Confirm the installed Nokri version from trusted deployment or package records.
- Verify the deployed release is outside the vendor-confirmed affected range.
- Review administrator password changes, new accounts, privilege changes, and unexpected logins.
- Check affected sites for unauthorized content, configuration changes, persistence, or data access.
- Confirm access restrictions remain effective until vendor remediation is deployed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-18550 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9WordfenceVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Vendor Notified
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/b03b7ea8-6485-495d-b815-2b7b882a75a2?source=cveCVE reference, Wordfence
- https://nokriwp.com/CVE reference, Wordfence
- https://themeforest.net/item/nokri-job-board-wordpress-theme/22677241CVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.