LowGHSA-3r8j-pmch-5j2hCVE-2019-16768

Internal exception message exposure for login action in Sylius

Published 5 Dec 2019 · Updated 8 Jul 2026

Is your project on an affected sylius/sylius?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<1.3.14
Fixed in
1.3.14
Update to the fixed version for your release line, for example:composer require sylius/sylius:^1.3.14
Affected
>=1.4.0 <1.4.10
Fixed in
1.4.10
Update to the fixed version for your release line, for example:composer require sylius/sylius:^1.4.10
Affected
>=1.5.0 <1.5.7
Fixed in
1.5.7
Update to the fixed version for your release line, for example:composer require sylius/sylius:^1.5.7
Affected
>=1.6.0 <1.6.3
Fixed in
1.6.3
Update to the fixed version for your release line, for example:composer require sylius/sylius:^1.6.3

Details

Internal exception message exposure for login action

Impact

Exception messages from internal exceptions (like database exception) are wrapped by \Symfony\Component\Security\Core\Exception\AuthenticationServiceException and propagated through the system to UI. Therefore, some internal system information may leak and be visible to the customer.

A validation message with the exception details will be presented to the user when one will try to log into the shop.

Patches

_Has the problem been patched? What versions should users upgrade to?_

Workarounds

The src/Sylius/Bundle/UiBundle/Resources/views/Security/_login.html.twig file should be overridden and lines https://github.com/Sylius/Sylius/blob/1.4/src/Sylius/Bundle/UiBundle/Resources/views/Security/_login.html.twig#L13-L17 should be replaced with

        {% if last_error %}
            <div class="ui left aligned basic segment">
                {{ messages.error(last_error.messageKey) }}
            </div>
        {% endif %}

The messageKey field should be used instead of the message.

Is GHSA-3r8j-pmch-5j2h in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected sylius/sylius, and gives you the command that fixes it.

More advisories for sylius/sylius

  • MediumCVE-2026-53639Sylius: IDOR on Shop Payment Request API endpoints · 9 Jul 2026
  • MediumCVE-2026-53638Sylius: Channel-based payment method restriction bypass on shop account orders API endpoint · 9 Jul 2026
  • MediumCVE-2026-53637Sylius: Cart FormComponent allows modification or deletion of an already-completed order · 9 Jul 2026
  • MediumCVE-2026-31825Sylius has a DQL Injection via API Order Filters · 11 Mar 2026
  • HighCVE-2026-31824Sylius has a Promotion Usage Limit Bypass via Race Condition · 11 Mar 2026
  • MediumCVE-2026-31823Sylius Vulnerable to Authenticated Stored XSS · 11 Mar 2026
All 24 advisories for sylius/sylius

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.