Security readout for executives and security teams
Plain-English summary
CVE-2026-2495 affects the WPNakama WordPress plugin. An unauthenticated visitor may be able to manipulate a REST API sorting parameter to read sensitive database information. The primary business risk is data exposure from WordPress sites using WPNakama versions up to and including 0.6.5.
Executive priority
Treat as urgent for any WordPress site using WPNakama. Prioritize public sites and sites containing customer, editorial, or operational data. If the plugin is absent, no action is needed beyond documentation.
Technical view
The flaw is SQL injection in the unauthenticated /wp-json/WPNakama/v1/boards REST API endpoint through the order parameter. The CVE attributes this to insufficient escaping and query preparation. CVSS 3.1 is 7.5, with network access, low complexity, no privileges, no user interaction, and high confidentiality impact.
Likely exposure
Internet-facing WordPress sites are exposed if they run WPNakama – Team and multi-Client Collaboration, Editorial and Project Management version 0.6.5 or earlier. Exposure depends on whether the plugin is installed and the REST endpoint is reachable.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The issue is still high priority because it is unauthenticated, network-reachable, and can expose database contents.
Researcher notes
The public description identifies CWE-89 and the affected parameter and endpoint. References include Wordfence, WordPress Trac source lines, and a Trac changeset. The provided bundle does not clearly name a fixed version, so remediation should be tied to current vendor repository guidance.
Mitigation direction
- Inventory WordPress sites for the WPNakama plugin and installed version.
- If version is 0.6.5 or earlier, follow vendor or WordPress plugin guidance immediately.
- Restrict or disable the plugin if no safe updated version is available.
- Review database and WordPress logs for suspicious access to the WPNakama boards REST endpoint.
Validation and detection
- Confirm whether WPNakama is installed on each WordPress instance.
- Record the plugin version and compare it to the affected range.
- Check whether the WPNakama REST API endpoint is externally reachable.
- Review vendor, Wordfence, and WordPress plugin repository entries for fixed-version guidance.
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-2495 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
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:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/7ffa92be-9d38-40d9-954d-d890136b5aa1?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/wpnakama/trunk/inc/class-wpnakama.php#L215CVE reference
- https://plugins.trac.wordpress.org/browser/wpnakama/tags/0.6.5/inc/class-wpnakama.php#L215CVE reference
- https://plugins.trac.wordpress.org/browser/wpnakama/trunk/inc/class-wpnakama-api.php#L209CVE reference
- https://plugins.trac.wordpress.org/browser/wpnakama/tags/0.6.5/inc/class-wpnakama-api.php#L209CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3461315%40wpnakama&new=3461315%40wpnakama&sfp_email=&sfph_mail=CVE reference
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 Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.