First published: Fri Feb 14 2014(Updated: )
Cross-site scripting (XSS) vulnerability in phpMyFAQ before 2.8.6 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
Credit: vultures@jpcert.or.jp
Affected Software | Affected Version | How to fix |
---|---|---|
phpMyFAQ | <=2.8.5 | |
phpMyFAQ | =1.0 | |
phpMyFAQ | =1.0.1 | |
phpMyFAQ | =1.0.1a | |
phpMyFAQ | =1.1.0 | |
phpMyFAQ | =1.1.1 | |
phpMyFAQ | =1.1.2 | |
phpMyFAQ | =1.1.3 | |
phpMyFAQ | =1.1.4 | |
phpMyFAQ | =1.1.4a | |
phpMyFAQ | =1.1.5 | |
phpMyFAQ | =1.2.0 | |
phpMyFAQ | =1.2.1 | |
phpMyFAQ | =1.2.2 | |
phpMyFAQ | =1.2.3 | |
phpMyFAQ | =1.2.4 | |
phpMyFAQ | =1.2.5 | |
phpMyFAQ | =1.2.5a | |
phpMyFAQ | =1.2.5b | |
phpMyFAQ | =1.3.0 | |
phpMyFAQ | =1.3.1 | |
phpMyFAQ | =1.3.2 | |
phpMyFAQ | =1.3.3 | |
phpMyFAQ | =1.3.4 | |
phpMyFAQ | =1.3.5 | |
phpMyFAQ | =1.3.6 | |
phpMyFAQ | =1.3.7 | |
phpMyFAQ | =1.3.8 | |
phpMyFAQ | =1.3.9 | |
phpMyFAQ | =1.3.9-pl1 | |
phpMyFAQ | =1.3.10 | |
phpMyFAQ | =1.3.11 | |
phpMyFAQ | =1.3.12 | |
phpMyFAQ | =1.3.13 | |
phpMyFAQ | =1.3.14 | |
phpMyFAQ | =1.4 | |
phpMyFAQ | =1.4-alpha1 | |
phpMyFAQ | =1.4-alpha2 | |
phpMyFAQ | =1.4.0 | |
phpMyFAQ | =1.4.0a | |
phpMyFAQ | =1.4.1 | |
phpMyFAQ | =1.4.2 | |
phpMyFAQ | =1.4.3 | |
phpMyFAQ | =1.4.4 | |
phpMyFAQ | =1.4.5 | |
phpMyFAQ | =1.4.6 | |
phpMyFAQ | =1.4.7 | |
phpMyFAQ | =1.4.8 | |
phpMyFAQ | =1.4.9 | |
phpMyFAQ | =1.4.10 | |
phpMyFAQ | =1.4.11 | |
phpMyFAQ | =1.5 | |
phpMyFAQ | =1.5-alpha1 | |
phpMyFAQ | =1.5-alpha2 | |
phpMyFAQ | =1.5-beta1 | |
phpMyFAQ | =1.5-beta2 | |
phpMyFAQ | =1.5-beta3 | |
phpMyFAQ | =1.5-rc1 | |
phpMyFAQ | =1.5-rc2 | |
phpMyFAQ | =1.5-rc3 | |
phpMyFAQ | =1.5-rc4 | |
phpMyFAQ | =1.5-rc5 | |
phpMyFAQ | =1.5.0 | |
phpMyFAQ | =1.5.1 | |
phpMyFAQ | =1.5.2 | |
phpMyFAQ | =1.5.3 | |
phpMyFAQ | =1.5.4 | |
phpMyFAQ | =1.5.5 | |
phpMyFAQ | =1.5.6 | |
phpMyFAQ | =1.5.7 | |
phpMyFAQ | =1.5.8 | |
phpMyFAQ | =1.5.9 | |
phpMyFAQ | =1.6.0 | |
phpMyFAQ | =1.6.1 | |
phpMyFAQ | =1.6.2 | |
phpMyFAQ | =1.6.3 | |
phpMyFAQ | =1.6.4 | |
phpMyFAQ | =1.6.5 | |
phpMyFAQ | =1.6.6 | |
phpMyFAQ | =1.6.7 | |
phpMyFAQ | =1.6.8 | |
phpMyFAQ | =1.6.9 | |
phpMyFAQ | =1.6.10 | |
phpMyFAQ | =1.6.11 | |
phpMyFAQ | =1.6.12 | |
phpMyFAQ | =2.0.0 | |
phpMyFAQ | =2.0.1 | |
phpMyFAQ | =2.0.2 | |
phpMyFAQ | =2.0.3 | |
phpMyFAQ | =2.0.4 | |
phpMyFAQ | =2.0.5 | |
phpMyFAQ | =2.0.6 | |
phpMyFAQ | =2.0.7 | |
phpMyFAQ | =2.0.8 | |
phpMyFAQ | =2.0.9 | |
phpMyFAQ | =2.0.10 | |
phpMyFAQ | =2.0.11 | |
phpMyFAQ | =2.0.12 | |
phpMyFAQ | =2.0.13 | |
phpMyFAQ | =2.0.14 | |
phpMyFAQ | =2.0.15 | |
phpMyFAQ | =2.0.16 | |
phpMyFAQ | =2.0.17 | |
phpMyFAQ | =2.5.0 | |
phpMyFAQ | =2.5.1 | |
phpMyFAQ | =2.5.2 | |
phpMyFAQ | =2.5.3 | |
phpMyFAQ | =2.5.4 | |
phpMyFAQ | =2.5.5 | |
phpMyFAQ | =2.5.6 | |
phpMyFAQ | =2.5.7 | |
phpMyFAQ | =2.6.0 | |
phpMyFAQ | =2.6.1 | |
phpMyFAQ | =2.6.2 | |
phpMyFAQ | =2.6.3 | |
phpMyFAQ | =2.6.4 | |
phpMyFAQ | =2.6.5 | |
phpMyFAQ | =2.6.6 | |
phpMyFAQ | =2.6.7 | |
phpMyFAQ | =2.6.8 | |
phpMyFAQ | =2.6.9 | |
phpMyFAQ | =2.6.10 | |
phpMyFAQ | =2.6.11 | |
phpMyFAQ | =2.6.12 | |
phpMyFAQ | =2.6.13 | |
phpMyFAQ | =2.6.14 | |
phpMyFAQ | =2.6.15 | |
phpMyFAQ | =2.6.16 | |
phpMyFAQ | =2.6.17 | |
phpMyFAQ | =2.6.18 | |
phpMyFAQ | =2.7.0 | |
phpMyFAQ | =2.7.1 | |
phpMyFAQ | =2.7.2 | |
phpMyFAQ | =2.7.3 | |
phpMyFAQ | =2.7.4 | |
phpMyFAQ | =2.7.5 | |
phpMyFAQ | =2.7.6 | |
phpMyFAQ | =2.7.7 | |
phpMyFAQ | =2.7.8 | |
phpMyFAQ | =2.7.9 | |
phpMyFAQ | =2.8.0 | |
phpMyFAQ | =2.8.1 | |
phpMyFAQ | =2.8.2 | |
phpMyFAQ | =2.8.3 | |
phpMyFAQ | =2.8.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-0814 is classified as a medium severity vulnerability due to the risk of cross-site scripting (XSS) issues.
To resolve CVE-2014-0814, upgrade to phpMyFAQ version 2.8.6 or later.
CVE-2014-0814 affects all versions of phpMyFAQ prior to version 2.8.6.
Attackers can exploit CVE-2014-0814 to inject arbitrary web scripts or HTML code, potentially leading to data theft or other malicious actions.
While the best solution is to upgrade, ensuring input validation and sanitization may provide a temporary workaround for CVE-2014-0814.