Skip to content
Fencer Intel
medium 6.5

GHSA-65v7-wg35-2qpm json

Sylius Resource Bundle Cross-Site Request Forgery vulnerability

published 2y ago modified last yr.

cvss
6.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Sylius 1.0.0 to 1.0.16, 1.1.0 to 1.1.8, 1.2.0 to 1.2.1 versions of AdminBundle and ResourceBundle are affected by this security issue.

This issue has been fixed in Sylius 1.0.17, 1.1.9 and 1.2.2. Development branch for 1.3 release has also been fixed.

### Description

The following actions in the admin panel did not require a CSRF token:

- marking order’s payment as completed - marking order’s payment as refunded - marking product review as accepted - marking product review as rejected

### Resolution

The issue is fixed by adding a required CSRF token to those actions.

We also fixed `ResourceController`‘s `applyStateMachineTransitionAction` method by adding a CSRF token check. If you use that action in the API context, you can disable it by adding `csrf_protection:` false to its routing configuration

Patch / fix

  • packagist sylius/resource-bundle 1.0.17, 1.1.9, 1.2.2

Is GHSA-65v7-wg35-2qpm in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
packagist sylius/resource-bundle
>=1.0.0, <1.0.17
>=1.1.0, <1.1.9
>=1.2.0, <1.2.2
1.0.17
1.1.9
1.2.2

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.