Skip to content

Product

wordpress insert-special-characters vulnerabilities

9 published CVES affecting wordpress insert-special-characters, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
9
Critical
3
High
6
Medium
0
Low
0
Unscored
0
CISA KEV
0

Latest wordpress insert-special-characters CVEs

Newest publication first

  1. CriticalCVSS 9.8 EPSS 3.2%

    The package simple-git before 3.15.0 are vulnerable to Remote Code Execution (RCE) when enabling the ext transport protocol, which makes it exploitable via clone() method. This vulnerability exists due to an incomplete fix of CVE-2022-24066.

  2. CriticalCVSS 9.8 EPSS 3.5%

    Prototype pollution vulnerability in function parseQuery in parseQuery.js in webpack loader-utils via the name variable in parseQuery.js. This affects all versions prior to 1.4.1 and 2.0.3.

  3. HighCVSS 7.5 EPSS 1.6%

    An exponential ReDoS (Regular Expression Denial of Service) can be triggered in the semver-regex npm package, when an attacker is able to supply arbitrary input to the test() method

  4. HighCVSS 7.8 EPSS 3.3%

    In Async before 2.6.4 and 3.x before 3.2.2, a malicious user can obtain privileges via the mapValues() method, aka lib/internal/iterator.js createObjectIterator prototype pollution.

  5. HighCVSS 7.5 EPSS 2.5% PoC

    guzzlehttp/psr7 is a PSR-7 HTTP message library. Versions prior to 1.8.4 and 2.1.1 are vulnerable to improper header parsing. An attacker could sneak in a new line character and pass untrusted values. The issue is patched in 1.8.4 and 2.1.1. There are currently no known workaroun...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.