phpMyFAQ sharing FAQ functionality can easily be abused for phishing purposes
Impact
The 'sharing FAQ' functionality allows any unauthenticated actor to misuse the phpMyFAQ application to send arbitrary emails to a large range of targets.
Source excerpt · OSVAffected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
| Affected range | Recorded fix |
|---|---|
| Earlier releases before 3.2.5Ecosystem versions | 3.2.5 |
Version evidence: OSV · GHSA-9hhf-xmcw-r3xg
View original version evidence (121 explicit versions)
Original source description
Summary
The 'sharing FAQ' functionality allows any unauthenticated actor to misuse the phpMyFAQ application to send arbitrary emails to a large range of targets.
Details
The phpMyFAQ application has a functionality where anyone can share a FAQ item to others. The front-end of this functionality allows any phpMyFAQ articles to be shared with 5 email addresses. The application will then send these 5 emails. However, there are no controls over what link and content are shared. Furthermore, any unauthenticated actor can perform this action. There is a CAPTCHA in place, however the amount of people you email with a single request is not limited to 5 by the backend. An attacker can thus solve a single CAPTCHA and send thousands of emails at once.
PoC
We send the following form and capture the request.

We now change the body to contain 50 email addresses instead of just 1, and send the request. The attacker can also change the body of the email to any phishing message.

Below are the logs of the email server, proving that all these emails were sent.

An attacker can also change the link that is sent in these emails. Making phishing even more possible.

Impact
An attacker can utilize the target application's email server to send phishing messages. This can get the server on a blacklist, causing all emails to end up in spam. It can also lead to reputational damages.
References
- Security advisory github.com/thorsten/phpMyFAQ/security/advisories/GHSA-9hhf-xmcw-r3xg
- Security advisory nvd.nist.gov/vuln/detail/CVE-2024-22208
- Patch github.com/thorsten/phpMyFAQ/commit/a34d94ab7b1be9256a9ef898f18ea6bfb63f6f1e
- Source reference github.com/thorsten/phpMyFAQ
- Security advisory www.phpmyfaq.de/security/advisory-2024-02-05