# CVE-2025-47933: Argo CD allows cross-site scripting on repositories page > Attackers can execute arbitrary scripts via the repository page, allowing them to perform actions on behalf of victims with repository edit permissions. - **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 29 May 2025 - **Updated:** 30 May 2025 - **Also known as:** BIT-argo-cd-2025-47933, GHSA-2hj5-g64g-fp6p, GO-2025-3720, RHSA-2025:8269 ## What is CVE-2025-47933? CVE-2025-47933 is a critical cross-site scripting vulnerability in Argoproj Argo Cd, published on 29 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Prior to versions 2.13.8, 2.14.13, and 3.0.4, an attacker can perform arbitrary actions on behalf of the victim via the API. Due to the improper filtering of URL protocols in the repository page, an attacker can achieve cross-site scripting with permission to edit the repository. This issue has been patched in versions 2.13.8, 2.14.13, and 3.0.4. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2025-47933? 12 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2, argo-cd and github.com/argoproj/argo-cd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd/v2` | Go | From 2.0.0-rc3 | 2.13.8, 2.14.13 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.0.0-rc3 | 2.13.8 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.0.0-rc3 | 2.13.8 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.14.0-rc1 | 2.14.13 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.14.0-rc1 | 2.14.13 | | `argo-cd` | Bitnami | From 1.2.0 | 2.13.8, 2.14.13, 3.0.4 | | `github.com/argoproj/argo-cd` | Go | From 1.2.0-rc1 | None | | `github.com/argoproj/argo-cd` | Go | From 1.2.0-rc1 to 1.8.7 | None | | `github.com/argoproj/argo-cd` | Go | From 1.2.0-rc1 to 1.8.7 | None | | `github.com/argoproj/argo-cd/v3` | Go | All versions | 3.0.4 | | `github.com/argoproj/argo-cd/v3` | Go | All versions | 3.0.4 | | `github.com/argoproj/argo-cd/v3` | Go | All versions | 3.0.4 | | `openshift-gitops-argocd-cli` | Red Hat:openshift_gitops:1.16::el8 | All versions | 0:1.16.1-26.el8 | | `openshift-gitops-argocd-cli-redistributable` | Red Hat:openshift_gitops:1.16::el8 | All versions | 0:1.16.1-26.el8 | | `microshift-gitops` | Red Hat:openshift_gitops:1.16::el9 | All versions | 0:1.16.1-10.el9 | | `microshift-gitops-release-info` | Red Hat:openshift_gitops:1.16::el9 | All versions | 0:1.16.1-10.el9 | | `openshift-gitops-argocd-cli` | Red Hat:openshift_gitops:1.16::el9 | All versions | 0:1.16.1-10.el9 | | `openshift-gitops-argocd-cli-redistributable` | Red Hat:openshift_gitops:1.16::el9 | All versions | 0:1.16.1-10.el9 | Products: Argoproj Argo Cd. ## How do I fix CVE-2025-47933? Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.13.8 or 2.14.13. ## Is CVE-2025-47933 being exploited? There is no known exploitation of CVE-2025-47933 in the wild and no public exploit code. ## Other vulnerabilities in Argoproj Argo Cd - [CVE-2025-55190](https://insights.sbomify.com/CVE-2025-55190/): Argo CD: Project API Token Exposes Repository Credentials (critical 10.0) - [CVE-2022-29165](https://insights.sbomify.com/CVE-2022-29165/): Argo CD will blindly trust JWT claims if anonymous access is enabled (critical 10.0) - [CVE-2023-40029](https://insights.sbomify.com/CVE-2023-40029/): Cluster secret might leak in cluster details page in Argo CD (critical 9.9) - [CVE-2022-24768](https://insights.sbomify.com/CVE-2022-24768/): Improper access control allows admin privilege escalation in Argo CD (critical 9.9) - [CVE-2024-21652](https://insights.sbomify.com/CVE-2024-21652/): Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-47933 and fix it if it is affected. What it is: CVE-2025-47933 is a critical cross-site scripting vulnerability in Argoproj Argo Cd, published on 29 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-47933 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v2 (Go): affected from 2.0.0-rc3; fixed in 2.13.8, 2.14.13 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.0.0-rc3; fixed in 2.13.8 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.0.0-rc3; fixed in 2.13.8 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.14.0-rc1; fixed in 2.14.13 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.14.0-rc1; fixed in 2.14.13 - argo-cd (Bitnami): affected from 1.2.0; fixed in 2.13.8, 2.14.13, 3.0.4 - github.com/argoproj/argo-cd (Go): affected from 1.2.0-rc1; no fix listed - github.com/argoproj/argo-cd (Go): affected from 1.2.0-rc1 up to 1.8.7; no fix listed - github.com/argoproj/argo-cd (Go): affected from 1.2.0-rc1 up to 1.8.7; no fix listed - github.com/argoproj/argo-cd/v3 (Go): affected all versions; fixed in 3.0.4 - github.com/argoproj/argo-cd/v3 (Go): affected all versions; fixed in 3.0.4 - github.com/argoproj/argo-cd/v3 (Go): affected all versions; fixed in 3.0.4 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-2025-47933/ (Markdown: https://insights.sbomify.com/CVE-2025-47933/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-47933 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-47933 - OSV: https://osv.dev/vulnerability/CVE-2025-47933 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-47933/ Summaries are generated and may contain mistakes; the official description above is the record.