Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2016-10960: Remote command execution in WordPress Wsecure before 2.4

Published Sep 16, 2019 · Updated 1 month 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
EPSS8.7%95th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Joomlaserviceprovider
IdentifiersCVE-2016-10960CWE-78

CVE-2016-10960 is an OS command injection vulnerability in the Wsecure plugin for WordPress before version 2.4. Shell metacharacters supplied through the publish parameter of the plugin's configuration handler can result in remote code execution.

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 permits remote execution of attacker-controlled code on the system hosting the vulnerable WordPress plugin. The execution privileges and specific effects on data or service availability are not established.

Mitigation

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

Disable or remove the vulnerable Wsecure plugin until it can be upgraded.

Remediation

Patch, then assume compromise.

Upgrade Wsecure to version 2.4 or later, outside the identified affected version range.

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.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
JoomlaserviceproviderWsecureapplication
FAQ

Frequently asked questions

Is CVE-2016-10960 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2016-10960?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2016-10960.
Is there a patch for CVE-2016-10960?
Upgrade Wsecure to version 2.4 or later, outside the identified affected version range.
What products are affected by CVE-2016-10960?
Joomlaserviceprovider Wsecure.
How severe is CVE-2016-10960?
CVE-2016-10960 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 8.7% (95th percentile) as of Oct 16, 2026.
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 activity2Community discussion across Reddit, Mastodon, and other social sources.