Fscripts is a narrowly scoped software vendor with a focused product footprint, centered on the Fantastic News application. The durable signal in its disclosure history centers on code-injection vulnerabilities, reflecting risks inherent to dynamic code generation and execution within the product. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Fscripts over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2005-3846HIGH SQL injection vulnerability in news.php in Fantastic News 2.1.1 and earlier allows remote attackers to execute arbitrary SQL commands via the category parameter. | Nov 26, 2005 | 7.5 | 30 | NO | YES |
CVE-2006-4285HIGH PHP remote file inclusion vulnerability in news.php in Fantastic News 2.1.3 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the CONFIG[script_path] p | Aug 22, 2006 | 7.5 | 29 | NO | YES |
CVE-2006-4671MEDIUM PHP remote file inclusion vulnerability in headlines.php in Fantastic News 2.1.4, and possibly earlier, allows remote attackers to execute arbitrary PHP code via a URL in the CONFI | Sep 11, 2006 | 6.8 | 27 | NO | YES |
CVE-2006-0972MEDIUM SQL injection vulnerability in news.php in Tony Baird Fantastic News 2.1.1 allows remote attackers to execute arbitrary SQL commands via the page parameter. NOTE: the category vec | Mar 3, 2006 | 5.0 | 22 | NO | YES |
CVE-2006-1154HIGH PHP remote file inclusion vulnerability in archive.php in Fantastic News 2.1.2 allows remote attackers to include arbitrary files via the CONFIG[script_path] variable. NOTE: 2.1.4 | Mar 10, 2006 | 7.5 | 20 | 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 Fscripts.
Media articles that mention a CVE ID that affects a product developed by Fscripts — matched by CVE ID, not by vendor name.