# CVE-2024-53855: User can view tickets from organizations they're not apart of in centurion_erp

> Authenticated users can view tickets from other organizations via API endpoints, exposing sensitive ITSM data.

- **Severity:** Low 1.9 (`CVSS:3.1/AV:P/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Nov 2024
- **Updated:** 27 Nov 2024
- **Also known as:** GHSA-h9q2-fcc6-r65c

## What is CVE-2024-53855?

CVE-2024-53855 is a low-severity missing authorization vulnerability in nofusscomputing centurion_erp, published on 27 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Centurion ERP (Enterprise Rescource Planning) is a simple application developed to provide open source IT management with a large emphasis on the IT Service Management (ITSM) modules. A user who is authenticated and has view permissions for a ticket, can view the tickets of another organization they are not apart of. Users with following permissions are applicable: 1. `view_ticket_change` permission can view change tickets from organizations they are not apart of. 2. `view_ticket_incident` permission can view incident tickets from organizations they are not apart of. 3. `view_ticket_request` permission can view request tickets from organizations they are not apart of. 4. `view_ticket_problem` permission can view problem tickets from organizations they are not apart of. The access to view the tickets from different organizations is only applicable when browsing the API endpoints for the tickets in question. The Centurion UI is not affected. Project Tasks, although a "ticket type" are also **Not** affected. This issue has been addressed in release version 1.3.1 and users are advised to upgrade. Users unable to upgrade may remove the ticket view permissions from users which would alleviate this vulnerability, if this is deemed not-viable, Upgrading is recommended.

Weakness: CWE-653 (Improper Isolation or Compartmentalization)

## Which versions are affected by CVE-2024-53855?

It affects 1 product.


Products: Nofusscomputing Centurion Erp.

## How do I fix CVE-2024-53855?

No fix has been published for CVE-2024-53855 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-53855 being exploited?

There is no known exploitation of CVE-2024-53855 in the wild and no public exploit code.

## Other vulnerabilities in nofusscomputing centurion_erp

- [CVE-2024-49373](https://insights.sbomify.com/CVE-2024-49373/): Centurion ERP user can view projects from organizations they're not apart of (medium 4.1)
- [CVE-2025-58156](https://insights.sbomify.com/CVE-2025-58156/): Centurion ERP users can view hashed authentication tokens that belong to other users (low 1.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53855 and fix it if it is affected.

What it is: CVE-2024-53855 is a low-severity missing authorization vulnerability in nofusscomputing centurion_erp, published on 27 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-53855 in the wild and no public exploit code.

Affected product: nofusscomputing centurion_erp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-53855/ (Markdown: https://insights.sbomify.com/CVE-2024-53855/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-53855
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-53855
- OSV: https://osv.dev/vulnerability/CVE-2024-53855

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-53855/
Summaries are generated and may contain mistakes; the official description above is the record.