Webgrind is a lightweight PHP-based profiling and code-visualization tool that exposes a web interface for analyzing application performance, creating a direct attack surface for unauthenticated or weakly authenticated access. Vulnerability disclosures center on input-handling and injection weaknesses—including path traversal, cross-site scripting, and OS command injection—that are characteristic of web-facing debugging and monitoring utilities where input validation may be secondary to utility. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Webgrind Project over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2018-12909HIGH Webgrind 1.5 relies on user input to display a file, which lets anyone view files from the local filesystem (that the webserver user has access to) via an index.php?op=fileviewer&f | Jun 27, 2018 | 7.5 | 42 | NO | YES |
CVE-2023-54339CRITICAL Webgrind 1.1 contains a remote command execution vulnerability that allows unauthenticated attackers to inject OS commands via the dataFile parameter in index.php. Attackers can ex | Jan 13, 2026 | 9.8 | 28 | NO | NO |
CVE-2012-1790MEDIUM Absolute path traversal vulnerability in Webgrind 1.0 and 1.0.2 allows remote attackers to read arbitrary files via a full pathname in the file parameter to index.php. | Mar 19, 2012 | 5.0 | 28 | NO | YES |
CVE-2023-54341MEDIUM Webgrind 1.1 and before contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious scripts via the file parameter in index.ph | Jan 13, 2026 | 6.1 | 22 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Webgrind Project.
Media articles that mention a CVE ID that affects a product developed by Webgrind Project — matched by CVE ID, not by vendor name.