CVE-2016-10960: The wsecure plugin before 2.4 for WordPress has remote code execution via shell metacharacters in the wsecure-config.php publish parameter.

PriorityP179high8.8CVSS 3.1

AVNACLPRLUINSUCHIHAH

ITWEXPLOITVulnCheck KEV

Exploited in the wild

EPSS

8.98%

94.6th percentile

The wsecure plugin before 2.4 for WordPress has remote code execution via shell metacharacters in the wsecure-config.php publish parameter.

Affected

1 ranges

Vendor	Product	Version range	Fixed in
joomlaserviceprovider	wsecure	< 2.4	2.4

Detection & IOCsextracted from sources · hover to see the quote

path/wp-content/plugins/wsecure/wsecure-config.php↗

commandwsecure_action=update&publish=";} header("{{name}}: CVE-2016-10960"); class WSecureConfig2 {var $test="↗

→Look for POST requests targeting /wp-content/plugins/wsecure/wsecure-config.php with the 'wsecure_action=update' parameter and shell metacharacters (e.g. semicolons, braces, quotes) in the 'publish' parameter body. ↗
→Detect exploitation attempts by monitoring HTTP responses for injected custom headers originating from the wsecure-config.php endpoint, indicating successful PHP code injection via the publish parameter. ↗
→Use the Google dork inurl:"/wp-content/plugins/wsecure" to identify potentially vulnerable WordPress installations exposed on the internet. ↗

·The vulnerability affects wsecure plugin versions strictly before 2.4; version 2.4 and above are not affected. ↗
·The exploit requires an authenticated (low-privilege) user session (CVSS PR:L), meaning unauthenticated exploitation is not indicated by available sources. ↗

CVSS provenance

nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvdv2.06.5MEDIUMAV:N/AC:L/Au:S/C:P/I:P/A:P

vulncheck8.8HIGH

CVEs like this are exactly what “Exploited This Week” covers.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.