PatchSiren cyber security CVE debrief
CVE-2026-75132 Tranquil_IT CVE debrief
A SQL injection vulnerability exists in WAPT Server versions 2.6.1.17834 and earlier. The vulnerability is located in the `columns` parameter of the GET `/api/v3/hosts` endpoint. An authenticated user with read-only privileges can exploit this vulnerability to inject arbitrary PostgreSQL expressions, bypass host scope restrictions, and access information from other rows or tables within the database.
- Vendor
- Tranquil_IT
- Product
- WAPT
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-31
- Original CVE updated
- 2026-09-08
- Advisory published
- 2026-08-31
- Advisory updated
- 2026-09-08
Who should care
Defenders responsible for WAPT Server deployments should assess exposure and prioritize patching or mitigation to prevent exploitation of this SQL injection vulnerability. This includes reviewing WAPT Server versions, verifying exposure, and applying patches or mitigations. Security teams and vulnerability management teams should also review compensating controls and monitor for suspicious activity.
Why it matters
CVE-2026-75132 is a SQL injection vulnerability in WAPT Server that allows an authenticated user with read-only privileges to inject arbitrary PostgreSQL expressions. Defenders responsible for WAPT Server deployments should assess exposure and prioritize patching or mitigation to prevent exploitation.
- Potential unauthorized access to sensitive data
- Possible bypass of host scope restrictions
- Risk of data tampering or exfiltration
- Need for verification of WAPT Server version and exposure
Technical summary
The SQL injection vulnerability in WAPT Server versions 2.6.1.17834 and earlier allows an authenticated user with read-only privileges to inject arbitrary PostgreSQL expressions. This can lead to bypassing host scope restrictions and accessing information from other rows or tables within the database. The vulnerability is located in the `columns` parameter of the GET `/api/v3/hosts` endpoint. Defenders should prioritize verifying exposure and applying patches or mitigations to prevent exploitation of this SQL injection vulnerability in WAPT Server.
Defensive priority
Defenders should prioritize verifying exposure and applying patches or mitigations to prevent exploitation of this SQL injection vulnerability in WAPT Server.
Recommended defensive actions
- Verify WAPT Server version and exposure to this vulnerability
- Apply patches or mitigations to prevent exploitation
- Monitor for suspicious activity on the `/api/v3/hosts` endpoint
- Review compensating controls for exposed systems
- Check relevant monitoring, detection, and logs for exposed assets
- Track exceptions and retest remediated assets
- Plan vendor-supported updates through normal change control
Evidence notes
The CVE record and NVD entry provide details on the SQL injection vulnerability in WAPT Server. Vendor documentation and a source reference provide additional context. Defenders should verify WAPT Server version and exposure, review vendor guidance, and monitor for suspicious activity. Evidence is limited to public CVE and NVD data, and additional verification is recommended.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-75132 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-75132
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-75132 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-75132
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/wapt-server-sql-injection-via-api-v3-hosts-endpoint
-
Source reference
Unverified legacy reference
URL: https://www.wapt.fr/en/doc/wapt-changelog.html
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.