GitHub Advisoryadvisory · Packagist

GHSA-9hhf-xmcw-r3xg phpMyFAQ sharing FAQ functionality can easily be abused for phishing purposes

MEDIUM Published 2024-02-05 Modified 2024-02-05 Official page ↗
Aliases
CVE-2024-22208
Ecosystem
Packagist
Packages
phpmyfaq/phpmyfaq
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Weaknesses
CWE-863
Reviewed
2024-02-05

Affected packages

• Packagist phpmyfaq/phpmyfaq: < 3.2.5 → fixed in 3.2.5

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.

Related

Alias · CVE (1)

  • CVE-2024-22208 phpMyFAQ is an Open Source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. vulnerability

Weakness · CWE (1)

  • CWE-863 Incorrect Authorization weakness

References