How severe is GHSA-25fx-mxc2-76g7?

GHSA-25fx-mxc2-76g7 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-25fx-mxc2-76g7?

GHSA-25fx-mxc2-76g7 affects the following packages: sylius/paypal-plugin (Packagist), sylius/paypal-plugin (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-25fx-mxc2-76g7?

Update sylius/paypal-plugin to 1.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-25fx-mxc2-76g7 is resolved across your whole dependency graph.

How do I detect GHSA-25fx-mxc2-76g7 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sylius/paypal-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-25fx-mxc2-76g7 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-25fx-mxc2-76g7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-25fx-mxc2-76g7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-25fx-mxc2-76g7?

GHSA-25fx-mxc2-76g7 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 75th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-25fx-mxc2-76g7?

GHSA-25fx-mxc2-76g7 is classified as Information Exposure (CWE-200), CWE-639 (CWE-639). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-25fx-mxc2-76g7 published, and has it been updated?

GHSA-25fx-mxc2-76g7 was published on October 6, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

Sylius PayPal Plugin allows unauthorized access to Credit card form, exposing payer name and not requiring 3DSGHSA-25fx-mxc2-76g7

HIGHFix: Sylius/PayPalPlugin@2adc46b

GHSA-25fx-mxc2-76g7 is a high-severity (CVSS 7.5) Information Exposure vulnerability in sylius/paypal-plugin. A fix is available for sylius/paypal-plugin — see the affected versions and patch details below.

Also known asCVE-2021-41120

Published

Oct 6, 2021

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘sylius/paypal-plugin🐘sylius/paypal-plugin

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

URL to the payment page done after checkout was created with autoincremented payment id (/pay-with-paypal/{id}) and therefore it was easy to access for anyone, not even the order's customer. The problem was, the Credit card form has prefilled "credit card holder" field with the Customer's first and last name. Additionally, the mentioned form did not require a 3D Secure authentication, as well as did not checked the result of the 3D Secure authentication.

Patches

The problem has been patched in Sylius/PayPalPlugin 1.2.4 and 1.3.1

Workarounds

One 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.

For more information

If you have any questions or comments about this advisory:

Open an issue in Sylius/PayPalPlugin issues
Email us at security at sylius dot com

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`sylius/paypal-plugin`	≥ 1.0.0&&< 1.2.4	1.2.4`composer require sylius/paypal-plugin:^1.2.4`
🐘Packagist	`sylius/paypal-plugin`	≥ 1.3.0&&< 1.3.1	1.3.1`composer require sylius/paypal-plugin:^1.3.1`

Affected Products

1 product · 2 configurations

Application

paypalsylius

≥ 1.3.0 && < 1.3.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sylius/paypal-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sylius/paypal-plugin to 1.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-25fx-mxc2-76g7 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Impact URL to the payment page done after checkout was created with autoincremented payment id (`/pay-with-paypal/{id}`) and therefore it was easy to access for anyone, not even the order's customer. The problem was, the Credit card form has prefilled "credit card holder" field with the Customer's first and last name. Additionally, the mentioned form did not require a 3D Secure authentication, as well as did not checked the result of the 3D Secure authentication. ### Patches The problem has been patched in Sylius/PayPalPlugin **1.2.4** and **1.3.1** ### Workarounds One can override a `sy