Apphp develops a modest line of web-based applications including calendar, content management, and hospitality platforms, with the recurring vulnerability signal centered on web-application input-handling and access-control weaknesses such as SQL injection, cross-site scripting, cross-site request forgery, and path traversal. Live severity, exploitation, and exposure details are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Apphp over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2010-3480MEDIUM Directory traversal vulnerability in index.php in ApPHP PHP MicroCMS 1.0.1, when magic_quotes_gpc is disabled, allows remote attackers to include and execute arbitrary local files | Sep 22, 2010 | 6.8 | 30 | NO | YES |
CVE-2010-3481MEDIUM Multiple SQL injection vulnerabilities in login.php in ApPHP PHP MicroCMS 1.0.1, when magic_quotes_gpc is disabled, allow remote attackers to execute arbitrary SQL commands via the | Sep 22, 2010 | 6.8 | 29 | NO | YES |
CVE-2010-4881MEDIUM Multiple cross-site request forgery (CSRF) vulnerabilities in calendar.class.php in ApPHP Calendar (ApPHP CAL) allow remote attackers to hijack the authentication of unspecified vi | Oct 7, 2011 | 6.8 | 21 | NO | NO |
CVE-2015-4713MEDIUM SQL injection vulnerability in ApPHP Hotel Site 3.x.x allows remote editors to execute arbitrary SQL commands via the pid parameter to index.php. | Jun 22, 2015 | 6.5 | 17 | NO | NO |
CVE-2010-4880MEDIUM Multiple cross-site scripting (XSS) vulnerabilities in calendar.class.php in ApPHP Calendar (ApPHP CAL) allow remote attackers to inject arbitrary web script or HTML via the (1) ca | Oct 7, 2011 | 4.3 | 16 | 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 Apphp.
Media articles that mention a CVE ID that affects a product developed by Apphp — matched by CVE ID, not by vendor name.