GHSA-WW33-JPPQ-QFRP

Vulnerability from github – Published: 2025-01-02 22:43 – Updated: 2025-08-14 19:34
VLAI?
Summary
phpMyFAQ Vulnerable to Stored HTML Injection at FAQ
Details

Summary

Due to insufficient validation on the content of new FAQ posts, it is possible for authenticated users to inject malicious HTML or JavaScript code that can impact other users viewing the FAQ. This vulnerability arises when user-provided inputs in FAQ entries are not sanitized or escaped before being rendered on the page.

Details

An attacker can inject malicious HTML content into the FAQ editor at http://localhost/admin/index.php?action=editentry, resulting in a complete disruption of the FAQ page's user interface. By injecting malformed HTML elements styled to cover the entire screen, an attacker can render the page unusable. This injection manipulates the page structure by introducing overlapping buttons, images, and iframes, breaking the intended layout and functionality.

PoC

  1. In the source code of a FAQ Q&A post, insert the likes of this snippet:
<p>&lt;--`<img src="&#96;"> --!&gt;</p>
<div style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"><form><button>HTML INJECTION 1<img> <img> <img> <img> <iframe></iframe></button>
<div style="xg-p: absolute; top: 0; left: 0; width: 100%; height: 100%;">x</div>
<button>HTML INJECTION 2<iframe></iframe> <iframe></iframe> </button></form></div>

image 2. A normal user would see the broken FAQ page, or otherwise manipulated by the attacker to present a different malicious page: image

A demo (fresh install overwrites every 24hours) here: https://roy.demo.phpmyfaq.de/content/1/24/en/24.html?

Impact

Exploiting this issue can lead to Denial of Service for legitimate users, damage to the user experience, and potential abuse in phishing or defacement attacks.

Severity ?
5.2 (Medium)
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:L
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "phpmyfaq/phpmyfaq"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.2.10"
            },
            {
              "last_affected": "4.0.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "thorsten/phpmyfaq"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.2.10"
            },
            {
              "last_affected": "4.0.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-56199"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-79",
      "CWE-80"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-01-02T22:43:40Z",
    "nvd_published_at": "2025-01-02T18:15:20Z",
    "severity": "MODERATE"
  },
  "details": "### Summary\nDue to insufficient validation on the content of new FAQ posts, it is possible for authenticated users to inject malicious HTML or JavaScript code that can impact other users viewing the FAQ. This vulnerability arises when user-provided inputs in FAQ entries are not sanitized or escaped before being rendered on the page.\n\n### Details\nAn attacker can inject malicious HTML content into the FAQ editor at http://localhost/admin/index.php?action=editentry, resulting in a complete disruption of the FAQ page\u0027s user interface. By injecting malformed HTML elements styled to cover the entire screen, an attacker can render the page unusable. This injection manipulates the page structure by introducing overlapping buttons, images, and iframes, breaking the intended layout and functionality. \n\n### PoC\n\n1. In the source code of a FAQ Q\u0026A post, insert the likes of this snippet:\n```\n\u003cp\u003e\u0026lt;--`\u003cimg src=\"\u0026#96;\"\u003e --!\u0026gt;\u003c/p\u003e\n\u003cdiv style=\"position: absolute; top: 0; left: 0; width: 100%; height: 100%;\"\u003e\u003cform\u003e\u003cbutton\u003eHTML INJECTION 1\u003cimg\u003e \u003cimg\u003e \u003cimg\u003e \u003cimg\u003e \u003ciframe\u003e\u003c/iframe\u003e\u003c/button\u003e\n\u003cdiv style=\"xg-p: absolute; top: 0; left: 0; width: 100%; height: 100%;\"\u003ex\u003c/div\u003e\n\u003cbutton\u003eHTML INJECTION 2\u003ciframe\u003e\u003c/iframe\u003e \u003ciframe\u003e\u003c/iframe\u003e \u003c/button\u003e\u003c/form\u003e\u003c/div\u003e\n```\n\n![image](https://github.com/user-attachments/assets/7c12ff40-1978-4dee-b501-c48f3ea2b9ba)\n2. A normal user would see the broken FAQ page, or otherwise manipulated by the attacker to present a different malicious page:\n![image](https://github.com/user-attachments/assets/4b815663-4836-4370-8b02-5b01bce71b0c)\n \nA demo (fresh install overwrites every 24hours) here: https://roy.demo.phpmyfaq.de/content/1/24/en/24.html?\n\n### Impact\nExploiting this issue can lead to Denial of Service for legitimate users, damage to the user experience, and potential abuse in phishing or defacement attacks.",
  "id": "GHSA-ww33-jppq-qfrp",
  "modified": "2025-08-14T19:34:18Z",
  "published": "2025-01-02T22:43:40Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-ww33-jppq-qfrp"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56199"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/thorsten/phpMyFAQ"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "phpMyFAQ Vulnerable to Stored HTML Injection at FAQ"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.