Yap maintains a blog platform product with a focused vulnerability footprint centered on input-handling defects in database interactions. The durable signal is SQL injection in the blog application, a class of weakness that reflects insufficient sanitization of user-supplied input in query construction. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Yap over time
Signals from CVEs in this vendor scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2009-1038MEDIUM Multiple SQL injection vulnerabilities in YAP Blog 1.1.1 allow remote attackers to execute arbitrary SQL commands via the (1) image_id parameter to comments.php, and remote authent | Mar 20, 2009 | 6.5 | 25 | NO | YES |
Signals from CVEs in this vendor scope (1 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Yap.
Media articles that mention a CVE ID that affects a product developed by Yap — matched by CVE ID, not by vendor name.