dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-46361

MEDIUM · 6.9 CVSS v3.1 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
phpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in search.twig where result.question and result.answerPreview are rendered with the raw filter, disabling autoescape protection. Attackers with FAQ editor privileges can inject HTML-entity-encoded payloads that bypass html_entity_decode(strip_tags()) processing in SearchController.php, executing arbitrary JavaScript in every visitor's browser context including administrators.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

phpMyFAQ before 4.1.2 contains a stored XSS vulnerability in the search.twig template where result.question and result.answerPreview are rendered using the raw filter, which disables Twig's autoescape protection. Attackers with FAQ editor privileges can inject HTML-entity-encoded payloads that bypass the html_entity_decode(strip_tags()) sanitization in SearchController.php, allowing arbitrary JavaScript execution in every visitor's browser including administrators.

MitigationRemove the raw filter from result.question and result.answerPreview in search.twig to restore proper autoescaping, and audit the sanitization logic in SearchController.php to prevent entity-encoding bypasses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify phpMyFAQ version
    Check the version.php or VERSION file in the phpMyFAQ installation directory, or look at the admin dashboard footer which often displays the version
    Affected if version is before 4.1.2
  2. Locate the search.twig template file
    Find the search.twig template in the phpMyFAQ installation, typically under templates/ or src/Template/ directory
    Affected if the file exists and contains result.question and result.answerPreview rendered with the raw filter
  3. Inspect raw filter usage in search.twig
    Open search.twig and search for 'result.question|raw' and 'result.answerPreview|raw' patterns
    Affected if either field uses the raw filter, disabling Twig's autoescape protection
  4. Verify SearchController.php sanitization logic
    Open SearchController.php and locate the html_entity_decode(strip_tags()) sanitization applied to search results
    Affected if the sanitization can be bypassed by HTML-entity-encoding payloads
  5. Confirm FAQ editor account access
    Check if any user accounts have FAQ editor or higher privileges in the phpMyFAQ user management system
    Affected if a user with FAQ editor privileges exists and can submit or edit FAQ content

You are affected if phpMyFAQ version is before 4.1.2 AND the search.twig template uses the raw filter on result.question or result.answerPreview, allowing a privileged user to inject XSS that bypasses the existing sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove the raw filter from result.question and result.answerPreview in search.twig to restore proper autoescaping, and audit the sanitization logic in SearchController.php to prevent entity-encoding bypasses.

Recommended fix Moderate confidence

phpMyFAQ 4.1.2 or later

  1. 1. Back up your current phpMyFAQ installation and database before performing any upgrade.
  2. 2. Download phpMyFAQ version 4.1.2 or a later stable release from the official repository (github.com/thomaskikus/phpMyFAQ or get the latest release from phpmyfaq.de).
  3. 3. Replace the existing phpMyFAQ files with the new version, preserving your configuration and any customizations.
  4. 4. Verify the upgrade was successful by logging into the admin panel.
  5. 5. Test the search functionality to confirm the raw filter vulnerability in search.twig has been patched.
  6. 6. Confirm that html_entity_decode(strip_tags()) in SearchController.php now properly sanitizes user input.
Caveat Review the changelog between your current version and 4.1.2 for any configuration or feature changes that may affect your setup

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46361 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46361 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data