Security readout for executives and security teams
Plain-English summary
CVE-2025-25692 is reported as a PHAR deserialization issue in PrestaShop 8.2.0. The claim is that an unauthenticated crafted POST request could lead to arbitrary code execution. Public evidence in the bundle is limited, so treat it as a credible e-commerce exposure requiring verification rather than confirmed mass exploitation.
Executive priority
Medium priority, rising to high for revenue-critical public stores on PrestaShop 8.2.0. The potential impact is serious, but the public record lacks confirmed exploitation and clear vendor remediation details.
Technical view
The CVE describes unsafe PHAR deserialization in PrestaShop 8.2.0's _getHeaders function, mapped to CWE-502 and CWE-77. CVSS 3.1 is 6.5 with network access, low complexity, no privileges, and no user interaction. The bundle does not identify affected CPEs, prerequisites, patch commits, or fixed versions.
Likely exposure
Internet-facing PrestaShop 8.2.0 stores are the primary suspected exposure. The source bundle does not confirm other affected versions, specific modules, hosting configurations, or CPEs.
Exploitation context
The CVE text claims arbitrary code execution via crafted POST request. CISA KEV status is false in the bundle, and no cited source establishes active exploitation in the wild.
Researcher notes
Evidence is thin beyond the CVE description and a third-party GitHub reference. Validate the vulnerable code path and fixed-version status from primary PrestaShop sources before broad claims. Avoid assuming all PrestaShop versions are affected.
Mitigation direction
- Inventory all PrestaShop deployments and identify any running version 8.2.0.
- Check PrestaShop vendor guidance for patches, fixed versions, or configuration mitigations.
- Prioritize upgrade or remediation for public stores handling payments or customer data.
- Apply temporary WAF and access controls where business-safe while awaiting vendor guidance.
- Increase monitoring for anomalous POST traffic to PrestaShop applications.
Validation and detection
- Confirm deployed PrestaShop versions from application metadata and release records.
- Review vendor repository or advisories for a matching fix or security note.
- Check web logs for unusual POST patterns without replaying payloads.
- Verify whether any compensating WAF rules are logging or blocking relevant requests.
- Recheck CVE and KEV records for changed exploitation or remediation status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-77: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-25692 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/PrestaShop/PrestaShopCVE reference, mitre
- https://github.com/3em0/cve_repo/blob/main/preshop/CVE-2025-25692.mdCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.