ZDF
Sign inSign up

Vulnerabilities

Vulnerability · GHSA-jf3w-9rmr-5rcr

Improper access control on the back-office notifications endpoint exposes customer data

Published Aug 18, 2026 · catalog updated Aug 18, 2026 · Improper access control on

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-jf3w-9rmr-5rcr. A missing EPSS score is not a low risk. Compare Improper access control on with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Improper access control on).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium4.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
composer prestashop/prestashop

### Impact This is a broken access control issue in the back office. The data behind the notification panel in the back-office header was served without checking the employee's permissions. Any employee account, including one whose profile grants no permission at all could therefore read recent customer and order information: customer names, order totals, carrier and order status. Shops that rely on restricted employee profiles to separate roles between staff, agencies or contractors are impacted. Exploitation requires a valid back-office session, so the shop front and anonymous visitors are not affected. The exposed data is personal, so the issue also carries a GDPR dimension for merchants. ### Patches The notification endpoints now require read permission on orders, customers or customer-service threads, and return a "forbidden" response otherwise. Upgrade to **PrestaShop 9.1.5** or **PrestaShop 8.2.8** ### Workarounds There is no configuration-level workaround: the endpoint is part of the standard back office and is called by every logged-in employee. ### References - [CWE-862: Missing Authorization](https://cwe.mitre.org/data/definitions/862.html) - Report a security issue: security-core@prestashop.com --- _Credits: this vulnerability was responsibly reported to the PrestaShop security team by **Robert Scherer**. We thank them for their report and for coordinating the disclosure with us._

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • composer prestashop/prestashop>= 8.0.0, < 8.2.8
  • composer prestashop/prestashop>= 9.0.0, < 9.1.5

How to fix GHSA-jf3w-9rmr-5rcr

  • Upgrade

    GHSA-jf3w-9rmr-5rcr lists a fix boundary at 8.2.8. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 8.2.8

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-jf3w-9rmr-5rcr. A missing EPSS score is not a low risk. Compare Improper access control on with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with >= 8.0.0, < 8.2.8, >= 9.0.0, < 9.1.5. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

PrestaShop security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 18, 2026 · Maintainer security tabs

    Detected

    ### Impact This is a broken access control issue in the back office. The data behind the notification panel in the back-office header was served without checking the employee's permissions. Any employee account, including one whose profile grants no permission at all could therefore read recent customer and order information: customer names, order totals, carrier and order status. Shops that rely

Sources

  • Maintainer security tabsVendor advisoryGHSA-jf3w-9rmr-5rcr

    ### Impact This is a broken access control issue in the back office. The data behind the notification panel in the back-office header was served without checking the employee's permissions. Any employee account, including one whose profile grants no permission at all could therefore read recent customer and order information: customer names, order totals, carrier and order status. Shops that rely

    github.com

Freshness

Last verified in this catalog Aug 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 1, 2026