LiveActive security incident?Get immediate response
CVE Record

CVE-2026-31917: WordPress WP ERP plugin <= 1.16.10 - SQL Injection vulnerability

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in weDevs WP ERP erp allows SQL Injection.This issue affects WP ERP: from n/a through <= 1.16.10.

HighCVSS 8.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-31917 is a high-severity SQL injection in the WordPress WP ERP plugin by weDevs, affecting versions through 1.16.10. An attacker with a valid account could potentially read sensitive database data and cause limited availability impact. Sources do not show confirmed active exploitation.

Executive priority

Treat as a near-term remediation priority for WordPress environments using WP ERP. The business risk is potential exposure of sensitive database information from authenticated access, but current sources do not show confirmed active exploitation.

Technical view

The issue is CWE-89 improper neutralization in WP ERP package “erp.” CVSS 3.1 is 8.5: network-accessible, low complexity, low privileges required, no user interaction, changed scope, high confidentiality impact, no integrity impact, and low availability impact.

Likely exposure

Externally reachable WordPress sites running WP ERP through version 1.16.10 are the primary concern, especially where untrusted or low-privileged users can authenticate.

Exploitation context

The CVSS vector indicates exploitation requires network access and a valid low-privilege account. The provided sources do not confirm public exploit availability or inclusion in CISA KEV.

Researcher notes

Source data identifies SQL injection in WP ERP through 1.16.10 with PR:L and C:H. No affected endpoint, proof-of-concept, fixed version, or exploitation evidence is included in the provided bundle.

Mitigation direction

  • Inventory WordPress sites for the WP ERP plugin and its installed version.
  • Prioritize sites running WP ERP 1.16.10 or earlier.
  • Check weDevs and Patchstack guidance for an update or official mitigation.
  • Limit access for untrusted authenticated users until vendor guidance is applied.
  • Review database and application logs for unusual authenticated activity.

Validation and detection

  • Confirm whether the WP ERP plugin is installed on each WordPress instance.
  • Record the exact WP ERP version from the admin interface or asset inventory.
  • Verify whether vendor guidance identifies a fixed version or workaround.
  • Check whether public user registration or low-trust accounts are enabled.
  • Review monitoring for abnormal database errors or suspicious plugin activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
description · low confidence lookup

Database 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 lookup
cve · low confidence lookup

CVE-2026-31917 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L3.14.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.5High
CVSS 3.1 vector shape for CVE-2026-31917Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
weDevsWP ERPerp, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

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.