Skip to main content

WPJAM Basic CVE-2026-57371

| EUVDEUVD-2026-43447 HIGH
Deserialization of Untrusted Data (CWE-502)
2026-07-13 Patchstack
8.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-priv WordPress account
  2. Delivery
    Craft malicious serialized PHP object
  3. Exploit
    Submit payload to vulnerable plugin input
  4. Execution
    Plugin deserializes untrusted data
  5. Persist
    POP gadget chain executes
  6. Impact
    Achieve code execution or data compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the WPJAM Basic plugin (versions n/a through 7.0) to be installed and active, and - per the CVSS PR:L metric - the attacker must hold at least a low-privileged authenticated account on the target WordPress site (e.g., a subscriber or contributor obtained via open self-registration). The attack is network-based (AV:N), low-complexity (AC:L), and needs no user interaction (UI:N), so once authenticated the attacker can send the malicious serialized payload directly. The realistic exploitation limit is twofold: the required authenticated foothold, and the dependence on a usable POP gadget chain in the installed WordPress/plugin stack for the object injection to reach high impact.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, score 8.8) indicates network-reachable, low-complexity exploitation requiring only low privileges and no user interaction, with full CIA impact - a genuinely serious combination for an internet-facing WordPress plugin. However, several risk-tempering signals apply: no EPSS score was provided, the CVE is not in CISA KEV (no confirmed active exploitation), and no public exploit code was referenced, so real-world weaponization is unproven. The PR:L requirement means an attacker needs some authenticated foothold (e.g., a subscriber/contributor account), which meaningfully limits mass, unauthenticated exploitation. In practice this rates as a real priority for sites running the plugin with open registration, but as moderate rather than emergency risk absent EPSS/KEV evidence of exploitation in the wild.

Exploit ScenarioDerived

An attacker registers or obtains a low-privilege account on a WordPress site running WPJAM Basic <= 7.0, then submits a crafted serialized PHP object to a plugin input that reaches unserialize(). When the plugin deserializes the payload, a POP gadget chain in WordPress or loaded plugins fires, letting the attacker read/write files, tamper with the database, or execute code. No public proof-of-concept exploit was identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 13, 2026

PHP Object Injection in the WPJAM Basic WordPress plugin (denishua) affects all versions up to and including 7.0, allowing an authenticated attacker to inject crafted serialized objects that are deserialized by the plugin. Reported by Patchstack and rated CVSS 8.8, it can lead to high-impact compromise (confidentiality, integrity, and availability) of the WordPress site, though exploitation requires at least low-level authenticated access. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.

RemediationAI

No vendor-released patch version was identified in the available data, so upgrade to a fixed release once denishua publishes one (monitor the plugin changelog and the Patchstack advisory at https://patchstack.com/database/Wordpress/Plugin/wpjam-basic/vulnerability/wordpress-wpjam-basic-plugin-7-0-php-object-injection-vulnerability). As immediate compensating controls, deactivate and remove the WPJAM Basic plugin if it is not essential (trade-off: loss of the plugin's functionality); restrict site registration and revoke untrusted low-privilege accounts to remove the PR:L foothold the attack needs (trade-off: limits open community features); and deploy a WordPress WAF such as Patchstack or an equivalent virtual patch to block PHP object-injection payloads to the plugin's endpoints (trade-off: may require tuning to avoid false positives). Because object-injection impact depends on POP gadget chains, also keeping WordPress core and all other plugins updated reduces available gadgets.

Affected VersionsENISA

WPJAM Basic 0 ≤7.0

Affected Packages

euvd wpjam_basic no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a classic CWE-502 Deserialization of Untrusted Data issue in PHP. WPJAM Basic (CPE cpe:2.3:a:denishua:wpjam_basic) passes attacker-influenced data into PHP's unserialize() (or an equivalent object-instantiating path) without validating or restricting the resulting object types. When such data is deserialized, PHP instantiates arbitrary objects, and any 'magic methods' (__wakeup, __destruct, __toString) present in the plugin, WordPress core, or other loaded plugins can be chained into a POP (Property-Oriented Programming) gadget chain. Depending on available gadgets, this escalates from object injection to file operations, SQL manipulation, or code execution - which is why the impact metrics are all rated High.

Know when Wpjam Basic gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable plugin endpoint (AV:N/AC:L) requiring a low-privilege authenticated account (PR:L); PHP object injection can reach full CIA compromise via gadget chains (C/I/A:H).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Deserialization of Untrusted Data vulnerability in denishua WPJAM Basic wpjam-basic allows Object Injection.This issue affects WPJAM Basic: from n/a through <= 7.0.

Executive ViewAI

Why It Matters

WPJAM Basic WordPress plugin versions through 7.0 contain a critical PHP object injection vulnerability (CVE-2026-57371, CVSS 8.8) that allows authenticated users to compromise WordPress site confidentiality, integrity, and availability. Organizations using this plugin face insider threat and account compromise risks, with potential for unauthorized data access, content manipulation, or service disruption.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: (1) uninstall or disable the WPJAM Basic plugin, especially on production systems; (2) restrict plugin functionality through WordPress role-based access controls, limiting access to trusted administrators with strong authentication; (3) implement Web Application Firewall rules to detect and block PHP serialized object injection patterns; (4) enable comprehensive logging and monitoring of authenticated user activities to detect anomalous behavior; (5) strengthen WordPress site hardening measures including multi-factor authentication and IP whitelisting for administrative access.

Threat Intelligence Overview

EPSS Score
0.5%
Top 60% exploitable
Prevalence
Low
niche WordPress plugin, limited deployment footprint outside its user base
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy