ZDF
Sign inSign up

Vulnerabilities

Security fix · GHSA-2cr4-vw9p-pjvf

Client IP address can be spoofed through the X-Forwarded-For header

Published Aug 18, 2026 · catalog updated Aug 18, 2026 · Client IP address can

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-2cr4-vw9p-pjvf. A missing EPSS score is not a low risk. Compare Client IP address can 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 (Client IP address can).
  • 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
High7.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 an IP address spoofing issue that can lead to access control bypass. When a shop runs behind a reverse proxy, a load balancer or a CDN, the visitor's real IP address is passed to PrestaShop through an HTTP header. PrestaShop read the wrong end of that header, the part controlled by the visitor, rather than the part appended by the shop's own proxy. Any visitor could therefore make the shop believe they were connecting from any address of their choosing, which undermines every feature relying on it: the maintenance-mode IP allow-list could be bypassed, security and audit logs could be filled with forged addresses, and third-party protections such as geolocation blocking, fraud scoring or rate limiting could be evaded. Shops served through a reverse proxy, a load balancer or a CDN are impacted, which covers most production deployments. Shops where visitors connect directly to the web server are not affected. No account and no user interaction are needed. ### Patches PrestaShop now reads the forwarding header from the end of the chain and ignores the private and reserved addresses belonging to internal infrastructure, so the value returned is the one added by the shop's own proxy, which a visitor cannot forge. Upgrade to **PrestaShop 9.1.5** or **PrestaShop 8.2.8** Correct IP handling is a shared responsibility between the application and the hosting setup, so the section below applies whether or not you have upgraded. ### Workarounds The issue can be fully mitigated at the proxy level, and we recommend doing so in addition to upgrading. Your front-end proxy must overwrite the forwarding header with the address it actually sees, instead of passing on whatever the visitor sent. **Nginx** If clients can reach Nginx directly, use instead. Never use , which forwards the visitor-supplied value untouched. **Apache** — use and declare only the proxies you trust: **CDN users** — make sure your origin only accepts connections from your CDN's address ranges, s

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-2cr4-vw9p-pjvf

  • Upgrade

    GHSA-2cr4-vw9p-pjvf 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-2cr4-vw9p-pjvf. A missing EPSS score is not a low risk. Compare Client IP address can 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

Nginx securityPrestaShop 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 an IP address spoofing issue that can lead to access control bypass. When a shop runs behind a reverse proxy, a load balancer or a CDN, the visitor's real IP address is passed to PrestaShop through an HTTP header. PrestaShop read the wrong end of that header, the part controlled by the visitor, rather than the part appended by the shop's own proxy. Any visitor could therefore ma

Sources

  • Maintainer security tabsVendor advisoryGHSA-2cr4-vw9p-pjvf

    ### Impact This is an IP address spoofing issue that can lead to access control bypass. When a shop runs behind a reverse proxy, a load balancer or a CDN, the visitor's real IP address is passed to PrestaShop through an HTTP header. PrestaShop read the wrong end of that header, the part controlled by the visitor, rather than the part appended by the shop's own proxy. Any visitor could therefore ma

    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