Mark Pilgrim's vulnerability footprint concentrates in feedparser, a widely embedded feed-parsing library used across syndication and content-aggregation applications. The observed weakness class centers on cross-site scripting risks during web page generation, reflecting the parsing and sanitization demands of processing untrusted feed content. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Mark Pilgrim over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2009-5065MEDIUM Cross-site scripting (XSS) vulnerability in feedparser.py in Universal Feed Parser (aka feedparser or python-feedparser) before 5.0 allows remote attackers to inject arbitrary web | Apr 11, 2011 | 4.3 | 26 | NO | YES |
CVE-2012-2921MEDIUM Universal Feed Parser (aka feedparser or python-feedparser) before 5.1.2 allows remote attackers to cause a denial of service (memory consumption) via a crafted XML ENTITY declarat | May 21, 2012 | 5.0 | 20 | NO | NO |
CVE-2011-1156MEDIUM feedparser.py in Universal Feed Parser (aka feedparser or python-feedparser) before 5.0.1 allows remote attackers to cause a denial of service (application crash) via a malformed D | Apr 11, 2011 | 5.0 | 18 | NO | NO |
CVE-2011-1158MEDIUM Cross-site scripting (XSS) vulnerability in feedparser.py in Universal Feed Parser (aka feedparser or python-feedparser) 5.x before 5.0.1 allows remote attackers to inject arbitrar | Apr 11, 2011 | 4.3 | 17 | NO | NO |
CVE-2011-1157MEDIUM Cross-site scripting (XSS) vulnerability in feedparser.py in Universal Feed Parser (aka feedparser or python-feedparser) 5.x before 5.0.1 allows remote attackers to inject arbitrar | Apr 11, 2011 | 4.3 | 17 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Mark Pilgrim.
Media articles that mention a CVE ID that affects a product developed by Mark Pilgrim — matched by CVE ID, not by vendor name.