Summary
Certain document-related endpoints in the open-source ERP system failed to enforce access validation, allowing unauthorized users to retrieve documents they should not be able to see.
When these endpoints are exposed over a network, an attacker can exploit the missing access checks to access sensitive business documents without proper authentication or authorization.
Affected context
The vulnerability occurs in deployments of the ERP platform where document-related HTTP endpoints are reachable (internally or externally) and rely on the application to enforce access control.
In affected versions, some of these endpoints do not consistently validate whether the caller is authenticated or has the required permissions for the requested document.
This becomes particularly risky in environments where the ERP instance is internet-facing or reachable from untrusted networks, or where multiple tenants or departments share the same deployment.
Exploit preconditions
- Attack surface: HTTP(S) endpoints exposed by the ERP application, typically as part of its web UI or API.
- Required access: Network-level access to the ERP service; in some cases, no valid user account may be required due to missing authentication or authorization checks.
- Trigger point: Directly invoking the affected endpoints (e.g., by crafted URLs or API calls) that fail to verify user identity and/or permissions for a requested document.
- Why exploitation is possible: The access control logic is incomplete or absent (CWE-284 / CWE-862), and in some flows authentication checks (CWE-306) are not enforced before serving document content.
Why this happens
The core issue is incomplete or missing enforcement of access control on specific document endpoints.
Instead of centralizing authorization checks and consistently verifying the caller's identity and permissions for each resource, the application exposes routes where:
- Authentication is not strictly required, or
- Authorization decisions are not performed or are performed using only weak, client-supplied identifiers.
This maps to:
- CWE-284: Improper Access Control – application logic does not adequately restrict access to protected resources.
- CWE-306: Missing Authentication for Critical Function – document access is allowed without first confirming the user's identity in some flows.
- CWE-862: Missing Authorization – the system fails to verify whether an authenticated user is allowed to access a specific document.
Conceptually, the bug class is "direct insecure object reference": endpoints expose internal document objects without consistently binding them to the requesting user's privileges.
Potential impact
- Unauthorized reading of sensitive business documents, such as invoices, contracts, HR files, or internal reports.
- Exposure of personal or regulated data that may trigger compliance incidents.
- Information disclosure that supports further attacks (e.g., reconnaissance, phishing, or fraud).
- Breach of tenant or departmental isolation in shared ERP deployments.
- Damage to customer trust and potential legal or contractual consequences due to data leakage.
General mitigation guidance
Effective mitigation focuses on enforcing consistent, centralized access control policies for all document endpoints:
- Require strong authentication for all endpoints that interact with sensitive resources and avoid unauthenticated document access paths.
- Apply authorization checks at the resource level: for each document request, validate that the user is entitled to access that specific object based on role, ownership, or tenancy.
- Use a unified access-control layer or middleware instead of ad-hoc permission checks scattered across controllers and handlers.
- Implement secure-by-default routing: new endpoints should inherit strict access requirements unless explicitly relaxed for non-sensitive resources.
- Avoid relying on client-supplied identifiers alone; tie document access decisions to server-side session and privilege information.
- Apply least privilege: design roles and permissions so users only see the minimum set of documents required for their duties.
How teams detect issues like this
Detection generally involves reviewing both code and behavior to identify endpoints lacking proper checks:
- Static analysis and code review:
- Search for controller or route handlers that serve documents but do not invoke authentication/authorization middleware or permission checks.
- Flag direct database or storage reads of document entities that bypass a shared access control service.
- Look for conditional logic that allows "public" access to document resources without clear justification.
- Policy and configuration review:
- Enforce framework-level security policies requiring authentication on all routes by default, with explicit allowlists for public endpoints.
- Use application security testing (DAST) tools or scripts to crawl endpoints and attempt access without valid credentials or with low-privileged accounts.
- Logging and monitoring:
- Enable detailed access logs for document endpoints and alert on unusual patterns (e.g., high-volume access from a single origin or access by unexpected accounts).
Automated code scanning tools, combined with manual review, can be configured to highlight any route that bypasses standard authentication/authorization mechanisms.

