# PrestaShop psgdpr through 1.4.3 GDPR Log Forgery

CVE record · `CVE-2026-92809`

- **Identifiers:** `CVE-2026-92809`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **CNA:** VulnCheck
- **Weakness (CWE):** [CWE-639](https://cwe.mitre.org/data/definitions/639.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Technologies:** [PrestaShop psgdpr](https://agentprime.io/advisories/technology/prestashop-psgdpr.md)
- **Published:** 16 Sept 2026
- **Updated:** 3 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: VulnCheck) at 16 Sept 2026, 20:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: PrestaShop. Product: psgdpr.
  - affected: `1.4.3 and earlier` (semver)
  - Other versions: unaffected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> PrestaShop psgdpr versions through 1.4.3 do not check that GDPR consent log entries belong to the authenticated customer. An authenticated attacker can submit other customers' identifiers to create forged consent records, which corrupts the audit logs. The source gives few details on the exact request involved. No fix is listed in the source.

Written 14 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 5.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`, from CNA (VulnCheck) (used for this record)
- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0035, the 29th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 16 Sept 2026, 20:32 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-92809)
- 16 Sept 2026, 21:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-92809)

## Sources

- [CVE List: CVE-2026-92809](https://www.cve.org/CVERecord?id=CVE-2026-92809)
- [NVD: CVE-2026-92809](https://nvd.nist.gov/vuln/detail/CVE-2026-92809)

### References from the CNA

- <https://github.com/PrestaShop/psgdpr/blob/v1.4.3/controllers/front/FrontAjaxGdpr.php#L28-L54> (technical-description)
- <https://github.com/PrestaShop/psgdpr/security/advisories/GHSA-wwqh-cf9m-347f> (vendor-advisory)
- <https://github.com/PrestaShop/psgdpr/releases/tag/v1.4.4> (patch, release-notes)
- <https://github.com/PrestaShop/psgdpr> (product)
- <https://www.vulncheck.com/advisories/prestashop-psgdpr-through-1.4.3-gdpr-log-forgery> (third-party-advisory)
- <https://github.com/geo-chen/oss/blob/main/prestashop.md#finding-1-idor---authenticated-customers-can-forge-gdpr-consent-records-for-arbitrary-customers> (technical-description, exploit)

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-92809>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-92809/>. Everything for agents: <https://agentprime.io/llms.txt>.
