CVE-2024-28106
published 2024-03-25CVE-2024-28106: phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. By manipulating the news parameter in a POST request, an…
PriorityP425medium5.4CVSS 3.1
AVNACLPRLUIRSCCLILAN
EPSS
0.54%
41.4th percentile
phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. By manipulating the news parameter in a POST request, an attacker can inject malicious JavaScript code. Upon browsing to the compromised news page, the XSS payload triggers. This vulnerability is fixed in 3.2.6.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| phpmyfaq | phpmyfaq | — | — |
| phpmyfaq | phpmyfaq | >= 3.2.5 < 3.2.6 | 3.2.6 |
| thorsten | phpmyfaq | — | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
phpMyFAQ Stored Cross-site Scripting at FAQ News Content
ghsa·2024-03-25
CVE-2024-28106 [MEDIUM] CWE-79 phpMyFAQ Stored Cross-site Scripting at FAQ News Content
phpMyFAQ Stored Cross-site Scripting at FAQ News Content
### Summary
By manipulating the news parameter in a POST request, an attacker can inject malicious JavaScript code. Upon browsing to the compromised news page, the XSS payload triggers.
### PoC
1. Edit a FAQ news, intercept the request and modify the `news` parameter in the POST body with the following payload: `%3cscript%3ealert('xssContent')%3c%2fscript%3e`
2. Browse to the particular news page and the XSS should pop up.
### Impact
This allows an attacker to execute arbitrary client side JavaScript within the context of another user's phpMyFAQ session
OSV
phpMyFAQ Stored Cross-site Scripting at FAQ News Content
osv·2024-03-25
CVE-2024-28106 [MEDIUM] phpMyFAQ Stored Cross-site Scripting at FAQ News Content
phpMyFAQ Stored Cross-site Scripting at FAQ News Content
### Summary
By manipulating the news parameter in a POST request, an attacker can inject malicious JavaScript code. Upon browsing to the compromised news page, the XSS payload triggers.
### PoC
1. Edit a FAQ news, intercept the request and modify the `news` parameter in the POST body with the following payload: `%3cscript%3ealert('xssContent')%3c%2fscript%3e`
2. Browse to the particular news page and the XSS should pop up.
### Impact
This allows an attacker to execute arbitrary client side JavaScript within the context of another user's phpMyFAQ session
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/thorsten/phpMyFAQ/commit/c94b3deadd87789389e1fad162bc3dd595c0e15ahttps://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6p68-36m6-392rhttps://github.com/thorsten/phpMyFAQ/commit/c94b3deadd87789389e1fad162bc3dd595c0e15ahttps://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-6p68-36m6-392r
2024-03-25
Published