Vulnerabilities
Summary — last 7 days
New vulnerabilities5,290▲ 2,541 vs. last week
Critical / high2,969▲ 1,639 vs. last week
New active exploitation (KEV)6▼ 2 vs. last week
Unscored (no CVSS)223▲ 49 vs. last week
6 results, sorted by published date (most recent first)
| CVE | Status | Severity | EPSS | Active exploitation | Affected technologies | Published ▼ | Modified | Description |
|---|---|---|---|---|---|---|---|---|
| Deferred | Medium (4.3) | 0.17% | — | Aipost AI WP WriterAI | 1/7/2025 | 6/17/2026 | Cross-Site Request Forgery (CSRF) vulnerability in aipost AI WP Writer ai-wp-writer allows Cross Site Request Forgery.This issue affects AI WP Writer: from n/a through <= 3.8.4.4. | |
| Deferred | Medium (4.3) | 0.23% | — | Aipost AicommentsAI | 12/13/2024 | 6/17/2026 | Cross-Site Request Forgery (CSRF) vulnerability in aipost AIcomments aicomments allows Cross Site Request Forgery.This issue affects AIcomments: from n/a through <= 1.4.1. | |
| Deferred | Medium (5.3) | 0.31% | — | Aipost AI WP WriterAI | 5/8/2024 | 6/17/2026 | Missing Authorization vulnerability in AIpost AI WP Writer.This issue affects AI WP Writer: from n/a through 3.6.5. | |
| Modified | High (7.5) | 2.0% | 💥 Exploit | Scripts24 IpostScripts24 Itgp | 8/6/2008 | 6/16/2026 | SQL injection vulnerability in go.php in Scripts24 iPost 1.0.1 and iTGP 1.0.4 allows remote attackers to execute arbitrary SQL commands via the id parameter in a report action. | |
| Modified | Medium (4.3) | 1.3% | — | Ipostmx 2005 | 6/19/2006 | 6/16/2026 | Multiple cross-site scripting (XSS) vulnerabilities in iPostMX 2005 2.0 and earlier allow remote attackers to inject arbitrary web script or HTML via the RETURNURL parameter in (1) userlogin.cfm and (2) account.cfm. | |
| Modified | High (7.5) | 1.1% | — | Ipostmx 2005 | 6/19/2006 | 9/23/2026 | Multiple SQL injection vulnerabilities in iPostMX 2005 2.0 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) forum parameter in messagepost.cfm and (2) topic parameter in topics.cfm. NOTE: this item was created based on information in a blog entry that was apparently removed after CVE… |