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

Check your stack
GHSA-qj6w-v29q-4rgxmedium5.4

MantisBT is Vulnerable to Stored XSS in Custom Field Textarea Values

Impact

Improper escaping of a textarea custom field's contents in the Update Issue page (bug_update_page.php) allows an attacker to inject HTML and, if CSP settings permit, execute arbitrary JavaScript when the page is loaded.

Source excerpt · OSV

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.

Affected rangeRecorded fix
Earlier releases before 2.28.2Ecosystem versions2.28.2

Version evidence: OSV · GHSA-qj6w-v29q-4rgx

View original version evidence (76 explicit versions)

Original source description

Improper escaping of a textarea custom field's contents in the Update Issue page (bug_update_page.php) allows an attacker to inject HTML and, if CSP settings permit, execute arbitrary JavaScript when the page is loaded.

Impact

Session theft leading to admin account takeover, full project data access.

  • Precondition: A textarea-type custom field must be configured for the project
  • Attacker: Authenticated user with bug report permission (low privilege)
  • Victim: Any user viewing the bug edit form, including administrators

Patches

  • 5fec0f448b7a7d7d539a6adb6dccceac4e4e4ab7

Workarounds

The default Content-Security Policy will block script execution.

References

Credits

Thanks to the following security researchers for independently discovering and responsibly reporting the issue, and providing a patch to fix it.

  • Thanks to Nozomu Sasaki (Paul) (@morimori-dev)
  • Tristan Madani (@TristanInSec) from Talence Security

References