# CVE-2024-39325: aimeos/ai-controller-frontend doesn't reset payment status in basket > Attackers can manipulate basket payment status after purchase due to missing reset logic, potentially leading to unauthorized state changes. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 2 Jul 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-m9gv-6p22-qgmj ## What is CVE-2024-39325? CVE-2024-39325 is a medium-severity vulnerability in aimeos ai-controller-frontend, published on 2 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description aimeos/ai-controller-frontend is the Aimeos frontend controller. Prior to versions 2024.04.2, 2023.10.9, 2022.10.8, 2021.10.8, and 2020.10.15, aimeos/ai-controller-frontend doesn't reset the payment status of a user's basket after the user completes a purchase. Versions 2024.04.2, 2023.10.9, 2022.10.8, 2021.10.8, and 2020.10.15 fix this issue. Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow) ## Which versions are affected by CVE-2024-39325? 8 open source packages ship an affected version, including aimeos/ai-controller-frontend. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `aimeos/ai-controller-frontend` | Packagist | All versions | 2020.10.15 | | `aimeos/ai-controller-frontend` | Packagist | All versions | 2020.10.15 | | `aimeos/ai-controller-frontend` | Packagist | From 2021.04.1 | 2021.10.8 | | `aimeos/ai-controller-frontend` | Packagist | From 2021.04.1 | 2021.10.8 | | `aimeos/ai-controller-frontend` | Packagist | From 2022.04.1 | 2022.10.8 | | `aimeos/ai-controller-frontend` | Packagist | From 2022.04.1 | 2022.10.8 | | `aimeos/ai-controller-frontend` | Packagist | From 2023.04.1 | 2023.10.9 | | `aimeos/ai-controller-frontend` | Packagist | From 2023.04.1 | 2023.10.9 | Products: Aimeos Aimeos Frontend Controller. ## How do I fix CVE-2024-39325? Upgrade aimeos/ai-controller-frontend to a fixed version for your release line: 2020.10.15, 2021.10.8, 2022.10.8 or 2023.10.9. ## Is CVE-2024-39325 being exploited? There is no known exploitation of CVE-2024-39325 in the wild and no public exploit code. ## Other vulnerabilities in aimeos ai-controller-frontend - [CVE-2024-39319](https://insights.sbomify.com/CVE-2024-39319/): aimeos/ai-controller-frontend has IDOR vulnerability in account profile page (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-39325 and fix it if it is affected. What it is: CVE-2024-39325 is a medium-severity vulnerability in aimeos ai-controller-frontend, published on 2 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-39325 in the wild and no public exploit code. Affected packages and fixed versions: - aimeos/ai-controller-frontend (Packagist): affected all versions; fixed in 2020.10.15 - aimeos/ai-controller-frontend (Packagist): affected all versions; fixed in 2020.10.15 - aimeos/ai-controller-frontend (Packagist): affected from 2021.04.1; fixed in 2021.10.8 - aimeos/ai-controller-frontend (Packagist): affected from 2021.04.1; fixed in 2021.10.8 - aimeos/ai-controller-frontend (Packagist): affected from 2022.04.1; fixed in 2022.10.8 - aimeos/ai-controller-frontend (Packagist): affected from 2022.04.1; fixed in 2022.10.8 - aimeos/ai-controller-frontend (Packagist): affected from 2023.04.1; fixed in 2023.10.9 - aimeos/ai-controller-frontend (Packagist): affected from 2023.04.1; fixed in 2023.10.9 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-39325/ (Markdown: https://insights.sbomify.com/CVE-2024-39325/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-39325 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-39325 - OSV: https://osv.dev/vulnerability/CVE-2024-39325 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-39325/ Summaries are generated and may contain mistakes; the official description above is the record.