What this page helps you verify fast
This hub clusters every indexed record for wSecure Lite so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin wSecure Lite (`wsecure`), including severity, CVE references, affected versions, and patch status.
Recent tracked CVEs on this page include CVE-2023-39987 and CVE-2016-10960, so operators can jump from disclosure to patch validation without scanning the full feed first.
Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.
wSecure Lite < 2.4 - Remote Code Execution
wSecure Lite <= 2.5 - Authenticated (Administrator+) Stored Cross-Site Scripting via settings
This hub clusters every indexed record for wSecure Lite so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The wSecure Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in versions up to, and including, 2.5 due to insufficient input sanitization and output...
The wsecure plugin before 2.4 for WordPress has remote code execution via shell metacharacters in the wsecure-config.php publish parameter.
Sorted by latest disclosure date so newly published issues surface first.
The wSecure Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in versions up to, and including, 2.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level per...
The wsecure plugin before 2.4 for WordPress has remote code execution via shell metacharacters in the wsecure-config.php publish parameter.