Security readout for executives and security teams
Plain-English summary
CVE-2026-1235 affects the WP eCommerce WordPress plugin through version 3.15.1. An unauthenticated attacker may be able to trigger unsafe PHP object handling through AJAX input. Impact depends on whether the site has a usable PHP “gadget” chain. Business urgency is moderate: internet-facing WordPress stores using this plugin should be identified and reviewed promptly.
Executive priority
Treat as a prompt WordPress ecommerce hygiene issue, not a confirmed emergency. Identify affected stores quickly, because exploitation requires no login if site conditions are favorable. Prioritize sites handling payments, customer data, or revenue-critical storefronts.
Technical view
The issue is CWE-502: deserialization of untrusted data. WP eCommerce through 3.15.1 unserializes user-controlled input via AJAX actions, enabling unauthenticated PHP Object Injection if a suitable gadget exists in the WordPress/plugin environment. CVSS 3.1 is 6.5, network exploitable, high attack complexity, no privileges or user interaction required, with limited confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on public WordPress sites running WP eCommerce version 3.15.1 or earlier. Risk is higher where additional plugins or themes provide exploitable PHP object gadget chains. The provided sources do not identify affected hosting platforms, specific configurations, or a confirmed fixed version.
Exploitation context
The WPScan reference is tagged with exploit-related information, but the source bundle does not state active exploitation, and the CVE is not listed as KEV. Exploitation is conditional because PHP Object Injection typically requires a suitable gadget chain already present on the site.
Researcher notes
Evidence is limited to the CVE record and WPScan entry. The affected range is stated as through 3.15.1, but the provided data does not name a fixed release or vendor mitigation. Validate gadget availability carefully without assuming exploitability across all installations.
Mitigation direction
- Inventory WordPress sites for WP eCommerce and record installed versions.
- If running version 3.15.1 or earlier, check vendor or WPScan guidance for updates.
- Remove or disable WP eCommerce where it is not business-critical.
- Review plugins and themes to reduce unnecessary PHP gadget exposure.
- Prioritize internet-facing ecommerce sites for remediation review.
Validation and detection
- Confirm whether WP eCommerce is installed on each WordPress site.
- Verify the installed plugin version against the affected range through 3.15.1.
- Review web logs for suspicious unauthenticated AJAX requests to WordPress endpoints.
- Check security monitoring for PHP deserialization or object injection alerts.
- Document whether vendor guidance or an updated plugin version is available.
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 lookupCVE-2026-1235 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:H/PR:N/UI:N/S:C/C:L/I:L/A:L
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.
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:H/PR:N/UI:N/S:C/C:L/I:L/A:L2.23.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/c7eb234e-3113-40db-a00d-358604d91e3f/CVE reference · exploit, vdb-entry
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.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.