# CVE-2023-44393: Piwigo Reflected XSS vulnerability > Reflected XSS in Piwigo allows attackers to inject malicious scripts executed by admin users, potentially leading to account takeover. - **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 9 Oct 2023 - **Updated:** 19 Sep 2024 - **Also known as:** GHSA-qg85-957m-7vgg ## What is CVE-2023-44393? CVE-2023-44393 is a critical cross-site scripting vulnerability in Piwigo Piwigo, published on 9 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Piwigo is an open source photo gallery application. Prior to version 14.0.0beta4, a reflected cross-site scripting (XSS) vulnerability is in the` /admin.php?page=plugins&tab=new&installstatus=ok&plugin_id=[here]` page. This vulnerability can be exploited by an attacker to inject malicious HTML and JS code into the HTML page, which could then be executed by admin users when they visit the URL with the payload. The vulnerability is caused by the insecure injection of the `plugin_id` value from the URL into the HTML page. An attacker can exploit this vulnerability by crafting a malicious URL that contains a specially crafted `plugin_id` value. When a victim who is logged in as an administrator visits this URL, the malicious code will be injected into the HTML page and executed. This vulnerability can be exploited by any attacker who has access to a malicious URL. However, only users who are logged in as administrators are affected. This is because the vulnerability is only present on the `/admin.php?page=plugins&tab=new&installstatus=ok&plugin_id=[here]` page, which is only accessible to administrators. Version 14.0.0.beta4 contains a patch for this issue. Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2023-44393? It affects 1 product. Products: Piwigo Piwigo. ## How do I fix CVE-2023-44393? No fix has been published for CVE-2023-44393 yet. Limit exposure of the affected software until one is available. ## Is CVE-2023-44393 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-44393 exists. Public exploit code: - Piwigo - Cross-Site Scripting (nuclei): http/cves/2023/CVE-2023-44393.yaml ## Other vulnerabilities in Piwigo Piwigo - [CVE-2014-4648](https://insights.sbomify.com/CVE-2014-4648/): Unspecified vulnerability in Piwigo before 2.6.3 has unknown impact and attack vectors, related to a "security failure." (critical 10.0) - [CVE-2023-33361](https://insights.sbomify.com/CVE-2023-33361/): SQL injection in n/a (critical 9.8) - [CVE-2023-33362](https://insights.sbomify.com/CVE-2023-33362/): SQL injection in n/a (critical 9.8) - [CVE-2020-19213](https://insights.sbomify.com/CVE-2020-19213/): SQL injection in n/a (critical 9.8) - [CVE-2021-32615](https://insights.sbomify.com/CVE-2021-32615/): SQL injection in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-44393 and fix it if it is affected. What it is: CVE-2023-44393 is a critical cross-site scripting vulnerability in Piwigo Piwigo, published on 9 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-44393 exists. Affected product: Piwigo Piwigo. 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-2023-44393/ (Markdown: https://insights.sbomify.com/CVE-2023-44393/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-44393 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-44393 - OSV: https://osv.dev/vulnerability/CVE-2023-44393 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-44393/ Summaries are generated and may contain mistakes; the official description above is the record.