CVE-2026-1235
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WP eCommerce WordPress plugin through 3.15.1 unserializes user input via ajax actions, which could allow unauthenticated users to perform PHP Object Injection when a suitable gadget is present on the blog.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe WP eCommerce WordPress plugin through version 3.15.1 has a PHP Object Injection vulnerability. The plugin unserializes user-supplied input via AJAX actions without proper validation, allowing unauthenticated attackers to inject malicious PHP objects if a suitable gadget chain exists in the WordPress environment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WP eCommerce plugin is installedLocate the wp-content/plugins/wp-e-commerce folder, or check the Plugins page in WordPress admin, or query the database wp_options table for option_name = 'active_plugins'Affected if Plugin folder or database entry exists indicating the plugin is installed
-
Check installed WP eCommerce versionOpen the main plugin file (wp-e-commerce.php) and look for the 'Version:' header comment, or check the Plugins page in WordPress admin, or query the wp_options table for option_name containing 'wp_e commerce_version'Affected if Version is 3.15.1 or lower (any version through 3.15.1)
-
Confirm AJAX endpoint is accessibleTest accessing the AJAX endpoint at /wp-admin/admin-ajax.php without authentication, or check if the wp-admin/admin-ajax.php file exists and responds to requestsAffected if AJAX endpoint responds to requests (returns JSON response or triggers plugin AJAX handlers)
-
Identify exposed AJAX actionsReview plugin source code for do_action calls tied to AJAX hooks (wp_ajax_ and wp_ajax_nopriv_), or grep for 'add_action' with 'wp_ajax' in the plugin directoryAffected if Plugin registers AJAX actions accessible to unauthenticated users (wp_ajax_nopriv_ hooks)
If WP eCommerce plugin version is 3.15.1 or lower and unauthenticated AJAX endpoints are accessible, the environment is affected by the PHP Object Injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the WP eCommerce plugin to the latest version beyond 3.15.1 when available. As a temporary measure, disable the plugin or restrict AJAX endpoints at the web server level until a patch is applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1235 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data