CVE-2026-10731
Deferred Deferred - Pending Action

SQL Injection in Two-Step Authentication System

Publication date: 2026-06-09

Last updated on: 2026-06-09

Assigner: Spanish National Cybersecurity Institute, S.A. (INCIBE)

Description
SQL injection in the ‘two_steps_auth_code’ parameter processed by the ‘twoStepsAuthVerification’ function within the ‘/user-login’ endpoint. The two-factor authentication (2FA) functionality can be accessed without prior authentication, allowing unauthenticated attackers to execute arbitrary SQL queries on the backend database. A successful exploit could lead to database enumeration, the unauthorised creation of privileged users, the modification or deletion of critical information, and denial-of-service conditions.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-09
Last Modified
2026-06-09
Generated
2026-06-29
AI Q&A
2026-06-09
EPSS Evaluated
2026-06-28
NVD
CVE-2026-10731
EUVD
EUVD-2026-35387

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
nemon nemon_trade_energy to 2.95.55 (inc)
nemon nemon_trade_energy_crm to 2.95.55 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-10731 is a critical SQL injection vulnerability found in the 'two_steps_auth_code' parameter handled by the 'twoStepsAuthVerification' function within the '/user-login' endpoint of Nemon Trade Energy and Nemon Trade Energy CRM versions up to 2.95.55.

This vulnerability allows unauthenticated attackers to execute arbitrary SQL queries on the backend database because the two-factor authentication (2FA) functionality can be accessed without prior authentication.

Impact Analysis

A successful exploit of this vulnerability could lead to several severe impacts including:

  • Database enumeration, allowing attackers to gather sensitive information about the database structure.
  • Unauthorized creation of privileged users, which could give attackers elevated access.
  • Modification or deletion of critical information, potentially disrupting business operations or causing data loss.
  • Denial-of-service conditions, which could make the service unavailable to legitimate users.
Mitigation Strategies

The vulnerability CVE-2026-10731 was fully mitigated by Nemon on May 26, 2026, through a centralized fix applied to their SaaS solution.

As the fix was applied centrally by the vendor without requiring customer action, immediate mitigation steps on your side are not necessary.

Compliance Impact

The SQL injection vulnerability in the 'two_steps_auth_code' parameter allows unauthenticated attackers to execute arbitrary SQL queries, potentially leading to unauthorized creation of privileged users, modification or deletion of critical data, and denial-of-service conditions.

Such unauthorized access and manipulation of sensitive data could result in non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive information against unauthorized access and data breaches.

However, there is no direct mention in the provided resources about specific impacts on compliance or regulatory violations.

Detection Guidance

This vulnerability involves SQL injection in the 'two_steps_auth_code' parameter within the '/user-login' endpoint, which can be tested by sending crafted HTTP requests to this endpoint to detect abnormal responses or database errors.

A common approach to detect SQL injection vulnerabilities is to use tools like curl or sqlmap to send payloads that test for SQL injection in the 'two_steps_auth_code' parameter.

  • Using curl to test for SQL injection: curl -X POST https://target-url/user-login -d 'two_steps_auth_code=1' OR '1'='1'
  • Using sqlmap to automate detection: sqlmap -u "https://target-url/user-login" --data="two_steps_auth_code=123" --risk=3 --level=5

Monitoring logs for unusual database errors or unexpected behavior when accessing the '/user-login' endpoint can also help detect exploitation attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-10731. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart