The wsecure plugin before 2.4 for WordPress has remote code execution via shell metacharacters in the wsecure-config.php publish parameter.
CVE-2016-10960
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fixed version is listed under Patch Availability — apply it.
Internet exposure
The internet-exposure footprint is temporarily unavailable — the KEV-Exposure radar's record for this CVE could not be loaded just now. That is not a finding of zero exposed services; please retry shortly.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHmedium confidence
- EG Risk
- 60EG Risk 60/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation40% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).Action: A fixed version is listed under Patch Availability. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 9.0%
- EPSS %ILE
- 95th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).
A fixed version is listed under Patch Availability. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 16, 2019
Last Modified
November 21, 2024
Advisory Details (1)
wsecure lite – WordPress plugin | WordPress.org
https://wordpress.org/plugins/wsecure/#developersVendor Advisories for CVE-2016-10960
Vendor advisories for this CVE are temporarily unavailable — the list could not be loaded just now. That is not a sign that none exist; please retry shortly.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| nuclei_template | http/cves/2016/CVE-2016-10960.yaml @ WordPress wSecure Lite < 2.4 - Remote Code Execution (fixes https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2016/CVE-2016-10960.yaml) | — | 2016-01-01 |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Publicly available exploits
(1 reference)Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Nucleihttp/cves/2016/CVE-2016-10960.yamlFirst seen Jan 1, 2016
WordPress wSecure Lite < 2.4 - Remote Code Execution
Open source ↗
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2016-10960?
When was CVE-2016-10960 disclosed?
Is CVE-2016-10960 actively exploited?
What is the CVSS score of CVE-2016-10960?
How do I remediate CVE-2016-10960?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2016-10960
Is Your Infrastructure Affected by CVE-2016-10960?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.