Pybluemonday

Vendor:

First CVE: Oct 18, 2021 · Active for 4 years

1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
9.8
Avg CVSS
Higher Avg CVSS than 87% of tracked products
0.0%
KEV Rate
Bottom 1%

Trends Over Time

The number and severity of CVEs published that impact Pybluemonday over time

Volume of CVEsAvg CVSS Base Score
First CVE
Oct 18, 2021
4 years ago
Most Recent CVE
Oct 18, 2021
1,740 days ago

CVE Severity & Scoring

Pybluemonday1 CVEs
All CVEs352,231 CVEs
Critical
Attack Vector
Local0 (0.0%)
Network1 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (100.0%)
High0 (0.0%)
Unknown0 (0.0%)
User Interaction
None1 (100.0%)
Unknown0 (0.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None1 (100.0%)
Unknown0 (0.0%)

Top CVEs

Signals from CVEs in this product scope (1 CVEs).

1 CVEs · Highest risk first

CVEPublishedCVSSRiskKEVExploit
The bluemonday sanitizer before 1.0.16 for Go, and before 0.0.8 for Python (in pybluemonday), does not properly enforce policies associated with the SELECT, STYLE, and OPTION eleme
Oct 18, 20219.829NONO

Exploit Exposure

Signals from CVEs in this product scope (1 CVEs).

CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%

Social Chatter

Signals from CVEs in this product scope (1 CVEs).

Media Mentions

Signals from CVEs in this product scope (1 CVEs).

Top CNAs Publishing CVEs For Pybluemonday

Versions

No cataloged versions.