How severe is CVE-2013-6418?

CVE-2013-6418 has a CVSS 2.0 base score of 5.8, rated medium severity.

Is CVE-2013-6418 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2013-6418?

CVE-2013-6418 affects Pywbem Project Pywbem. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2013-6418?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2013-6418 published?

CVE-2013-6418 was published on 2014-05-05 and last updated on 2026-06-17.

CVE-2013-6418

CVE-2013-6418 is a medium-severity vulnerability in Pywbem Project Pywbem with a CVSS 2.0 base score of 5.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-20.

Key facts

Severity: Medium (CVSS 2.0 base score 5.8)
EPSS exploit prediction: 2% (75th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-20
Affected product: Pywbem Project Pywbem
Published: 2014-05-05
Last modified: 2026-06-17

Description

PyWBEM 0.7 and earlier uses a separate connection to validate X.509 certificates, which allows man-in-the-middle attackers to spoof a peer via an arbitrary certificate.

Frequently asked questions

What is CVE-2013-6418?: PyWBEM 0.7 and earlier uses a separate connection to validate X.509 certificates, which allows man-in-the-middle attackers to spoof a peer via an arbitrary certificate.
How severe is CVE-2013-6418?: CVE-2013-6418 has a CVSS 2.0 base score of 5.8, rated medium severity.
Is CVE-2013-6418 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2013-6418?: CVE-2013-6418 affects Pywbem Project Pywbem. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2013-6418?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2013-6418 published?: CVE-2013-6418 was published on 2014-05-05 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:pywbem_project:pywbem:*:*:*:*:*:*:*:*

More vulnerabilities in Pywbem Project Pywbem

CVE-2013-6444 — Medium (CVSS 5.8): PyWBEM 0.7 and earlier does not verify that the server hostname matches a domain name in the subject's Common Name (CN)…

All CVEs affecting Pywbem Project Pywbem →

Other CWE-20 (Improper Input Validation) vulnerabilities

CVE-2026-48316 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Input Validation vulnerability that could…
CVE-2026-48281 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Input Validation vulnerability that could…
CVE-2026-48277 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Input Validation vulnerability that could…
CVE-2026-48055 — Critical (CVSS 10.0): Streambert is a cross-platform Electron Desktop App to stream and download any video media. In versions 2.4.0 and…
CVE-2026-34910 — Critical (CVSS 10.0): A malicious actor with access to the network could exploit an Improper Input Validation vulnerability found in UniFi OS…
CVE-2026-33587 — Critical (CVSS 10.0): Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and…

Browse all CWE-20 (Improper Input Validation) vulnerabilities →