Skip to main content
CVE-2025-51605VulnerabilityPublished

CVE-2025-51605: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

AI-suggested

Immediate mitigation steps include updating Shopizer to a patched version once available from the vendor. In the absence of an official patch, organizations should implement strict CORS policies by configuring the server to whitelist only trusted origins in the Access-Control-Allow-Origin header and avoid reflecting client-supplied Origin headers. Additionally, the Access-Control-Allow-Credentials header should be disabled unless absolutely necessary and only for trusted origins. Web application firewalls (WAFs) can be configured to detect and block suspicious cross-origin requests with unexpected Origin headers. Organizations should also conduct thorough audits of their Shopizer deployments to identify any unauthorized data access or anomalies. Monitoring network traffic for unusual cross-origin requests and implementing Content Security Policy (CSP) headers can help reduce the attack surface. Finally, educating users about the risks of visiting untrusted websites while authenticated to critical services can reduce the likelihood of exploitation.

Description

An issue was discovered in Shopizer 3.2.7. The server's CORS implementation reflects the client-supplied Origin header verbatim into Access-Control-Allow-Origin without any whitelist validation, while also enabling Access-Control-Allow-Credentials: true. This allows any malicious origin to make authenticated cross-origin requests and read sensitive responses.

References

Community reviews

Loading reviews…