Skip to content

thorsten/phpmyfaq Unintended File Download Triggered by Embedded Frames

Moderate severity GitHub Reviewed Published Dec 13, 2024 in thorsten/phpMyFAQ • Updated Dec 13, 2024

Package

composer thorsten/phpmyfaq (Composer)

Affected versions

< 3.2.10

Patched versions

3.2.10

Description

Summary

A vulnerability exists in the FAQ Record component where a privileged attacker can trigger a file download on a victim's machine upon page visit by embedding it in an <iframe> element without user interaction or explicit consent.

Details

In http://localhost/admin/index.php?action=editentry&id=20&lang=en, where a FAQ record is either created or edited, an attacker can insert an iframe, as "source code", pointing to a prior "malicious" attachment that the attacker has uploaded via FAQ "new attachment" upload, such that any page visits to this FAQ will trigger an automated download (from the edit screen, download is automated; from the faq page view as a normal user, depending on the browser, a pop up confirmation may be presented before the actual download. Firebox browser, for instance, does not require any interactions).
image

PoC

  1. create a new FAQ record and upload a "malicious" file - in my case, I uploaded an eicar file. take note of the uri, ie

    <iframe "index.php?action=attachment&id=2"
    image

  2. in the FAQ record, insert a "source code" blob using the "< >" button

  3. insert in the following snippet:

    <iframe src="index.php?action=attachment&id=2"></iframe>

    and save FAQ record

  4. once the edit page reloads, the malicious code will be downloaded onto the local machine without user interaction:
    image

(uploaded a POC for easy demonstration: https://roy.demo.phpmyfaq.de/admin/index.php?action=editentry&id=20&lang=en
although a fresh installation overwrites this demo instance every 24 hours)

(as a logged in normal user, visit: https://roy.demo.phpmyfaq.de/content/1/20/en/20.html)

Impact

Malicious code or binaries could be dropped on visitors' machines when visiting the FAQ platform. Take a worm or ransomware for instance.

References

@thorsten thorsten published to thorsten/phpMyFAQ Dec 13, 2024
Published by the National Vulnerability Database Dec 13, 2024
Published to the GitHub Advisory Database Dec 13, 2024
Reviewed Dec 13, 2024
Last updated Dec 13, 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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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:H/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.043%
(11th percentile)

Weaknesses

CVE ID

CVE-2024-55889

GHSA ID

GHSA-m3r7-8gw7-qwvc

Source code

Credits

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