# CVE-2021-41120: Unauthorized access to Credit card form in sylius/paypal-plugin

> Attackers can access unauthenticated credit card forms via predictable URLs to view customer names, exposing personally identifiable information.

- **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:** 5 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-25fx-mxc2-76g7

## What is CVE-2021-41120?

CVE-2021-41120 is a high-severity missing authorization vulnerability in Sylius PayPalPlugin, published on 5 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

sylius/paypal-plugin is a paypal plugin for the Sylius development platform. In affected versions the URL to the payment page done after checkout was created with autoincremented payment id (/pay-with-paypal/{id}) and therefore it was easy to predict. The problem is that the Credit card form has prefilled "credit card holder" field with the Customer's first and last name and hence this can lead to personally identifiable information exposure. Additionally, the mentioned form did not require authentication. The problem has been patched in Sylius/PayPalPlugin 1.2.4 and 1.3.1. If users are unable to update they can override a sylius_paypal_plugin_pay_with_paypal_form route and change its URL parameters to (for example) {orderToken}/{paymentId}, then override the Sylius\PayPalPlugin\Controller\PayWithPayPalFormAction service, to operate on the payment taken from the repository by these 2 values. It would also require usage of custom repository method. Additionally, one could override the @SyliusPayPalPlugin/payWithPaypal.html.twig template, to add contingencies: ['SCA_ALWAYS'] line in hostedFields.submit(...) function call (line 421). It would then have to be handled in the function callback.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2021-41120?

4 open source packages ship an affected version, including sylius/paypal-plugin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sylius/paypal-plugin` | Packagist | From 1.0.0 | 1.2.4 |
| `sylius/paypal-plugin` | Packagist | From 1.0.0 | 1.2.4 |
| `sylius/paypal-plugin` | Packagist | From 1.3.0 | 1.3.1 |
| `sylius/paypal-plugin` | Packagist | From 1.3.0 | 1.3.1 |

Products: Sylius Paypal.

## How do I fix CVE-2021-41120?

Upgrade sylius/paypal-plugin to a fixed version for your release line: 1.2.4 or 1.3.1.

## Is CVE-2021-41120 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41120 and fix it if it is affected.

What it is: CVE-2021-41120 is a high-severity missing authorization vulnerability in Sylius PayPalPlugin, published on 5 Oct 2021. 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-2021-41120 in the wild and no public exploit code.

Affected packages and fixed versions:
- sylius/paypal-plugin (Packagist): affected from 1.0.0; fixed in 1.2.4
- sylius/paypal-plugin (Packagist): affected from 1.0.0; fixed in 1.2.4
- sylius/paypal-plugin (Packagist): affected from 1.3.0; fixed in 1.3.1
- sylius/paypal-plugin (Packagist): affected from 1.3.0; fixed in 1.3.1

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-2021-41120/ (Markdown: https://insights.sbomify.com/CVE-2021-41120/index.md)
```

## Sources

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

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