Security readout for executives and security teams
Plain-English summary
Public-facing WordPress sites using Nokri 1.6.6 or earlier may allow unauthenticated attackers to bypass access controls. The supplied 9.8 CVSS assessment indicates potential compromise of confidentiality, integrity, and availability without user interaction. Specific vulnerable functions and observed attack activity are not documented in the supplied evidence.
Executive priority
Treat confirmed Nokri 1.6.6-or-earlier deployments as an immediate investigation and remediation priority, especially when internet-facing. Business owners should prepare temporary containment if no verified fix is available. Do not claim compromise solely from the severity score.
Technical view
The issue is described as remotely exploitable broken access control with low attack complexity, no required privileges, and no user interaction. The CVSS vector rates confidentiality, integrity, and availability impacts as high. However, the structured affected-version metadata is incomplete, and the listed CWE-640 does not clearly align with the broken-access-control description.
Likely exposure
Highest exposure is on internet-accessible WordPress installations running Nokri 1.6.6 or earlier. Confirm versions locally because the narrative identifies this range while the structured affected data says “n/a” and defaults unspecified versions to unaffected.
Exploitation context
The source bundle does not identify active exploitation, and this CVE is not listed as KEV in the supplied record. It also provides no public exploit details or vulnerable endpoint information. Absence of cited exploitation evidence should not be interpreted as proof that exploitation is impossible.
Researcher notes
Important technical details are missing: affected functions, root cause, discovery method, fixed version, and exploitation evidence. The CWE-640 assignment concerns weak password recovery and appears inconsistent with the broader broken-access-control description. Validate scope against current vendor or Patchstack guidance before making endpoint-specific conclusions.
Mitigation direction
- Inventory WordPress sites using Nokri and record each installed version.
- Check Patchstack and vendor guidance for a confirmed fixed version or official mitigation.
- Apply a verified update promptly when vendor guidance confirms the remediation.
- If no fix is confirmed, consider disabling or replacing Nokri where operationally feasible.
Validation and detection
- Confirm production and staging Nokri versions through authorized administrative inventory.
- Verify protected Nokri functions reject unauthenticated access in a controlled staging environment.
- Review relevant logs for unexplained anonymous access to privileged actions.
- After remediation, retest authorization boundaries and confirm the deployed version.
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-640: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCVE-2026-66691 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.9PatchstackVulnerability 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.
- 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://patchstack.com/database/wordpress/theme/nokri/vulnerability/wordpress-nokri-theme-1-6-6-broken-access-control-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
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.
Weak Password Recovery Mechanism for Forgotten Password
Weak Password Recovery Mechanism for Forgotten Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.