Security readout for executives and security teams
Plain-English summary
WPJAM Basic versions through 7.0.1 are reported vulnerable to SQL injection, potentially exposing WordPress database information and disrupting service. The supplied assessment rates it 9.3 critical. The sources disagree on whether an attacker needs subscriber access, so organizations should treat reachable installations as urgent until vendor guidance clarifies authentication requirements.
Executive priority
Prioritize same-day inventory and containment for internet-facing sites. Accelerate remediation where WPJAM Basic 7.0.1 or earlier is confirmed. There is no supplied evidence of active exploitation, but potential database disclosure and service impact justify urgent action.
Technical view
CVE-2026-61966 is classified as CWE-89 SQL injection in WPJAM Basic through 7.0.1. The CVSS 3.1 vector indicates network access, low complexity, no privileges or user interaction, high confidentiality impact, and low availability impact. However, the description calls it subscriber SQL injection, creating an authentication inconsistency requiring validation.
Likely exposure
Exposure is limited to WordPress sites running WPJAM Basic 7.0.1 or earlier. Internet-accessible sites warrant the fastest review. The bundle provides no CPEs, lists affected versions as “n/a,” and also records a default status of unaffected, so inventory confirmation is essential.
Exploitation context
The bundle does not report CISA KEV listing or confirmed active exploitation. No conclusion about exploitation in the wild should be drawn. The critical score and remote, low-complexity CVSS characteristics indicate serious potential risk, while the conflicting privilege information leaves practical attack prerequisites uncertain.
Researcher notes
Evidence is incomplete and internally inconsistent: the title sets the boundary at 7.0.1, while structured versions are “n/a” and default status is unaffected. The description requires subscriber access, but CVSS states no privileges. No fixed version, patch details, attack endpoint, or exploitation telemetry is supplied.
Mitigation direction
- Identify every WordPress installation using WPJAM Basic and record its installed version.
- Check WPJAM Basic and Patchstack guidance for a confirmed fixed release or vendor mitigation.
- Update to a vendor-confirmed safe version when available and follow normal backup procedures.
- Restrict or disable the plugin where business impact permits until remediation is confirmed.
- Increase monitoring for unusual database activity and suspicious WordPress requests.
Validation and detection
- Verify plugin versions from authoritative WordPress inventory or administrative records.
- Confirm whether vulnerable plugin functionality is reachable from unauthenticated or subscriber contexts.
- Review database and web logs for unexplained queries, errors, or access patterns.
- After remediation, confirm the vulnerable version is absent across all environments.
- Document the authentication inconsistency and reassess when vendor details become available.
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-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration 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-61966 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.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
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:C/C:H/I:N/A:L3.94.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
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/plugin/wpjam-basic/vulnerability/wordpress-wpjam-basic-plugin-7-0-1-sql-injection-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.