ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2016-10960

joomlaserviceprovider wsecure Improper Input Validation

Published Oct 8, 2025 · catalog updated Oct 8, 2025 · joomlaserviceprovider wsecure Improper Input

Patch now

CVE-2016-10960 is in the CISA known-exploited catalog. Confirm joomlaserviceprovider wsecure Improper Input against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (joomlaserviceprovider wsecure Improper Input).
  • No version range is stored. A customer cannot check an installed version against this record.
Severity
Unknown—
Known exploitation
CISA KEV and VulnCheck KEV
EPSS
8.98%
Remediation
Remediation guidance
Affected products
vendor joomlaserviceprovider wsecure

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

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor joomlaserviceprovider wsecureversion unspecified

How to fix CVE-2016-10960

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2016-10960 is in the CISA known-exploited catalog. Confirm joomlaserviceprovider wsecure Improper Input against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Which versions are affected?

Affected version ranges are not on this record. Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

What should an analyst verify?

No weakness class is stored. EPSS 8.98%. The CISA KEV listing is the exploitation evidence. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

WordPress security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 8, 2025 · VulnCheck KEV

    Detected

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

  2. Oct 8, 2025 · CISA KEV

    Known exploited

    Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Sources

  • CVE.orgVulnerability recordCVE-2016-10960

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2016-10960

    30-day exploitation probability 9.0%

    first.org
  • VulnCheck KEVConfirmed exploitationCVE-2016-10960

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

    vulncheck.com

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.