CVE-2026-129171 in NginxPulseinfo

Summary

by MITRE • 11/13/2026

NginxPulse 1.5.0 before 1.6.26 contains an unauthenticated sql injection vulnerability that allows remote attackers to append SQL via the id and locationType parameters of /api/stats/:type. Attackers can close the quoted table-name identifier and use error-based output to read database contents, and read or write server files via PostgreSQL superuser functions.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/13/2026

The NginxPulse application version 1.5.0 prior to release 1.6.26 is affected by a critical unauthenticated SQL injection vulnerability located within the /api/stats/:type endpoint. This flaw arises from insufficient input validation and sanitization of user-supplied data, specifically targeting the id and locationType parameters passed via HTTP requests. Because this API endpoint does not enforce authentication requirements for these specific parameters, any remote attacker with network access to the service can exploit this weakness without needing valid credentials. The vulnerability allows an adversary to inject arbitrary SQL commands directly into the backend database queries executed by the application server.

The technical mechanism of exploitation involves manipulating the id and locationType fields to break out of their expected data types or string contexts within the underlying SQL query structure. By carefully crafting input strings, attackers can close existing quoted table-name identifiers or string literals in the original query. This structural manipulation enables the injection of additional SQL statements that are then executed by the database engine. The exploitation strategy often leverages error-based output techniques, where the application's response includes detailed error messages generated by the database server when processing malformed queries. These verbose errors reveal schema details and data contents, allowing the attacker to enumerate database structures and extract sensitive information such as user credentials, configuration settings, or proprietary business logic stored within the database.

Beyond simple data exfiltration, this vulnerability poses a severe risk of full system compromise due to the potential for server-side code execution. If the backend database is running PostgreSQL with superuser privileges assigned to the application's database account, an attacker can leverage specific built-in functions available in that environment. By injecting commands that invoke these high-privilege functions, such as those used for file I/O operations or system command execution, the attacker can read arbitrary files from the server filesystem or write malicious content to disk. This capability effectively bypasses application-level controls and grants the attacker direct interaction with the underlying operating system infrastructure, potentially leading to complete control over the host machine hosting NginxPulse.

The operational impact of this vulnerability is extensive, encompassing confidentiality breaches, integrity violations, and potential availability disruptions. The ability to read database contents compromises the privacy and security of all data managed by NginxPulse, including sensitive user information and internal metrics. Furthermore, the capability to write files or execute system commands allows attackers to plant backdoors, modify application configurations, or disrupt services, thereby affecting business continuity. This level of access undermines trust in the platform's reliability and exposes organizations to significant regulatory compliance risks if personal data is compromised.

To mitigate this vulnerability, immediate action must be taken by upgrading NginxPulse to version 1.6.26 or later, where these input validation flaws have been addressed. In environments where an upgrade cannot be implemented immediately, network-level controls such as Web Application Firewalls should be configured to detect and block SQL injection patterns targeting the /api/stats endpoint. Additionally, implementing strict parameterized queries or prepared statements in future development cycles will prevent similar issues by ensuring that user input is treated strictly as data rather than executable code. It is also recommended to review database permissions for the application account, adhering to the principle of least privilege by removing superuser rights and restricting file I/O capabilities where they are not explicitly required for normal operation.

This vulnerability aligns with Common Weakness Enumeration identifier CWE-89, which classifies improper neutralization of special elements used in an SQL command. From a tactical perspective, it corresponds to MITRE ATT&CK techniques related to SQL Injection and potentially Command and Scripting Interpreter if file system access is achieved through database functions. Understanding these mappings helps security teams prioritize remediation efforts based on established industry standards for vulnerability management and threat mitigation strategies.

Responsible

VulnCheck

Reservation

11/13/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00414

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!