# CVE-2023-33960: OpenProject vulnerable to project identifier information leakage through robots.txt > Attackers can view public project identifiers via robots.txt even when login is required, exposing internal project names. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Jun 2023 - **Updated:** 8 Jan 2025 - **Also known as:** BIT-openproject-2023-33960, GHSA-xjfc-fqm3-95q8 ## What is CVE-2023-33960? CVE-2023-33960 is a high-severity vulnerability in opf openproject, published on 1 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description OpenProject is web-based project management software. For any OpenProject installation, a `robots.txt` file is generated through the server to denote which routes shall or shall not be accessed by crawlers. These routes contain project identifiers of all public projects in the instance. Prior to version 12.5.6, even if the entire instance is marked as `Login required` and prevents all truly anonymous access, the `/robots.txt` route remains publicly available. Version 12.5.6 has a fix for this issue. Alternatively, users can download a patchfile to apply the patch to any OpenProject version greater than 10.0 As a workaround, one may mark any public project as non-public and give anyone in need of access to the project a membership. Weakness: CWE-319 (Cleartext Transmission of Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2023-33960? 1 open source package ship an affected version, including openproject. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `openproject` | Bitnami | All versions | 12.5.6 | Products: Openproject Openproject. ## How do I fix CVE-2023-33960? Upgrade openproject to 12.5.6 or later. ## Is CVE-2023-33960 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33960 exists. Public exploit code: - OpenProject < 12.5.4 - Project Identifiers Exposure (nuclei): http/cves/2023/CVE-2023-33960.yaml ## Other vulnerabilities in opf openproject - [CVE-2026-34717](https://insights.sbomify.com/CVE-2026-34717/): OpenProject: SQL Injection in Cost Reporting =n Operator via parse_number_string (critical 9.9) - [CVE-2026-25763](https://insights.sbomify.com/CVE-2026-25763/): Command Injection on OpenProject repositories leads to Remote Code Execution (critical 9.4) - [CVE-2026-24685](https://insights.sbomify.com/CVE-2026-24685/): OpenProject has Argument Injection on Repository module that allows Arbitrary File Write (critical 9.4) - [CVE-2026-32698](https://insights.sbomify.com/CVE-2026-32698/): OpenProject has a SQL Injection via Custom Field Name that can be chained to Remote Code Execution (critical 9.1) - [CVE-2026-32703](https://insights.sbomify.com/CVE-2026-32703/): OpenProject's repository files are served with the MIME type allowing them to be used to bypass Content Security Policy (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-33960 and fix it if it is affected. What it is: CVE-2023-33960 is a high-severity vulnerability in opf openproject, published on 1 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33960 exists. Affected packages and fixed versions: - openproject (Bitnami): affected all versions; fixed in 12.5.6 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-2023-33960/ (Markdown: https://insights.sbomify.com/CVE-2023-33960/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-33960 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-33960 - OSV: https://osv.dev/vulnerability/CVE-2023-33960 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-33960/ Summaries are generated and may contain mistakes; the official description above is the record.