Skip to main content
Mallory
HighVulnerability

CVE-2026-32513: PHP Object Injection in JS Archive List

Published Mar 25, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS0.30%23rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-32513CWE-502 · Deserialization of Untrusted Data

CVE-2026-32513 is a deserialization of untrusted data vulnerability in the Miguel Useche JS Archive List WordPress plugin (jquery-archive-list-widget). The issue affects JS Archive List versions through 6.1.7. According to the provided record, unsafe handling of untrusted serialized data allows PHP object injection. No specific vulnerable function or code path was provided in the available content.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an authenticated attacker with low privileges to trigger PHP object injection over the network without user interaction. Depending on the gadget chains available in the target WordPress environment, this can result in severe compromise, including unauthorized access to sensitive data, modification of application state or content, arbitrary code execution in some environments, and denial of service. The provided CVSS v3.1 vector indicates high impact to confidentiality, integrity, and availability.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable and remove the JS Archive List plugin where feasible. Restrict access to plugin functionality to only trusted users, minimize low-privilege account access, and monitor for suspicious requests targeting plugin endpoints or parameters that may carry serialized input. Reducing installed plugins and libraries that expose usable PHP object gadget chains may also reduce exploitability, though this is not a substitute for patching.

Remediation

Patch, then assume compromise.

Update JS Archive List to a version newer than 6.1.7 if a vendor-fixed release is available. Because the provided content only states that versions through 6.1.7 are affected and does not identify a specific patched version, the exact fixed version is currently not available from the supplied data. Review vendor or Patchstack advisories for the definitive patched release and apply it promptly.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-32513 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-32513 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-32513?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-32513.
Is there a patch for CVE-2026-32513?
Update JS Archive List to a version newer than 6.1.7 if a vendor-fixed release is available. Because the provided content only states that versions through 6.1.7 are affected and does not identify a specific patched version, the exact fixed version is currently not available from the supplied data.
How severe is CVE-2026-32513?
CVE-2026-32513 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.30% (23rd percentile) as of Sep 25, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.