Skip to content

phpMyFAQ User Removal Page Allows Spoofing Of User Details

Moderate severity GitHub Reviewed Published Feb 5, 2024 in thorsten/phpMyFAQ • Updated Feb 5, 2024

Package

composer phpmyfaq/phpmyfaq (Composer)

Affected versions

< 3.2.5

Patched versions

3.2.5

Description

Summary

phpMyFAQ's user removal page allows an attacker to spoof another user's detail, and in turn make a compelling phishing case for removing another user's account.

Details

phpMyFAQ's user removal page allows an attacker to spoof another user's detail, and in turn make a compelling phishing case for removing another user's account. Whilst the front-end of this page doesn't allow changing the form details, an attacker can utilize a proxy to intercept this request and submit other data. Upon submitting this form, an email is sent to the administrator informing them that this user wants to delete their account. An administrator has no way of telling the difference between the actual user wishing to delete their account or the attacker issuing this for an account they do not control.

PoC

We are logged in as hacker and visit /user/request-removal. This brings us to the following page. We are not able to change the username, Your name and Your email address fields on this page.
image

However, we intercept this request using a proxy tool such as BurpSuite.
image

We can now edit the request before sending it. We change the fields mentioned above to the details of another user, and send the request.
image

This results in the following email being sent to the administrator. For them, it looks like the victim wants to delete their account.
image

Impact

The impact of this vulnerability is that administrators cannot trust the emails sent by the platform. An attacker can easily make a compelling case to perform phishing and get victim accounts deleted.

References

@thorsten thorsten published to thorsten/phpMyFAQ Feb 5, 2024
Published by the National Vulnerability Database Feb 5, 2024
Published to the GitHub Advisory Database Feb 5, 2024
Reviewed Feb 5, 2024
Last updated Feb 5, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H

EPSS score

0.046%
(17th percentile)

Weaknesses

CVE ID

CVE-2024-22202

GHSA ID

GHSA-6648-6g96-mg35

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.