GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GHSA-ww33-jppq-qfrpmedium5.2

phpMyFAQ Vulnerable to Stored HTML Injection at FAQ

Check your stack

The advisory, in context

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.

Affected 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.

Ecosystem versions

From 3.2.10 through 4.0.1 (inclusive)

No fix recorded for this interval.

14 explicitly affected versions

3.2.10, 4.0.0, 4.0.0-RC, 4.0.0-RC.2, 4.0.0-RC.3, 4.0.0-RC.4, 4.0.0-RC.5, 4.0.0-alpha, 4.0.0-alpha.2, 4.0.0-alpha.3, 4.0.0-alpha.4, 4.0.0-beta, 4.0.0-beta.2, 4.0.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "3.2.10"
        },
        {
          "last_affected": "4.0.1"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "3.2.10",
    "4.0.0",
    "4.0.0-RC",
    "4.0.0-RC.2",
    "4.0.0-RC.3",
    "4.0.0-RC.4",
    "4.0.0-RC.5",
    "4.0.0-alpha",
    "4.0.0-alpha.2",
    "4.0.0-alpha.3",
    "4.0.0-alpha.4",
    "4.0.0-beta",
    "4.0.0-beta.2",
    "4.0.1"
  ]
}
Ecosystem versions

From 3.2.10 through 4.0.1 (inclusive)

No fix recorded for this interval.

14 explicitly affected versions

3.2.10, 4.0.0, 4.0.0-RC, 4.0.0-RC.2, 4.0.0-RC.3, 4.0.0-RC.4, 4.0.0-RC.5, 4.0.0-alpha, 4.0.0-alpha.2, 4.0.0-alpha.3, 4.0.0-alpha.4, 4.0.0-beta, 4.0.0-beta.2, 4.0.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "3.2.10"
        },
        {
          "last_affected": "4.0.1"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "3.2.10",
    "4.0.0",
    "4.0.0-RC",
    "4.0.0-RC.2",
    "4.0.0-RC.3",
    "4.0.0-RC.4",
    "4.0.0-RC.5",
    "4.0.0-alpha",
    "4.0.0-alpha.2",
    "4.0.0-alpha.3",
    "4.0.0-alpha.4",
    "4.0.0-beta",
    "4.0.0-beta.2",
    "4.0.1"
  ]
}

References