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

CVE-2026-46363

MEDIUM · 5.4 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 →
58/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 FAQ creation and update endpoints that bypass sanitization through encode-decode cycles. The vulnerability allows authenticated attackers with FAQ_ADD permission to inject malicious script tags via question or answer parameters, which execute in every visitor's browser when FAQ content is rendered with the raw Twig filter.

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 has a stored XSS vulnerability in FAQ creation/update endpoints where authenticated users with FAQ_ADD permission can inject malicious scripts via question or answer parameters. The attack succeeds because sanitization is bypassed through encode-decode cycles, and the payload executes when content is rendered using the raw Twig filter.

MitigationUpgrade to phpMyFAQ 4.1.2 or later; alternatively, remove or replace the raw Twig filter usage on user-submitted content and implement proper output encoding to prevent encode-decode bypass.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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. Confirm phpMyFAQ installation and version
    Locate the phpMyFAQ installation directory and check the version file (commonly version.php or similar file containing the version string). Compare the installed version number against 4.1.2.
    Affected if The installed version is below 4.1.2 (e.g., 4.1.1, 4.0.x, 3.x).
  2. Verify FAQ creation endpoint exists
    Check if the FAQ creation/update endpoints are accessible in the web application. Look for routes or pages handling FAQ add/edit functionality, typically found in admin or user-facing FAQ management sections.
    Affected if The FAQ creation or update functionality is present and enabled in the application.
  3. Confirm authentication and FAQ_ADD permission
    Review user role or permission configuration to determine if any authenticated users have FAQ_ADD permission. Check the user group/permission settings in the phpMyFAQ admin panel or database.
    Affected if Authenticated users are able to be granted or already have FAQ_ADD permission capability.
  4. Inspect Twig template for raw filter usage
    Examine the Twig template files that render FAQ question and answer content. Look for usage of the 'raw' filter (e.g., {{ content|raw }}) applied to user-submitted FAQ fields.
    Affected if The raw Twig filter is applied to question or answer content that originates from user input.

A user is affected if phpMyFAQ version is below 4.1.2, FAQ creation/update endpoints are enabled, authenticated users can access them with FAQ_ADD permission, and the raw Twig filter is used to render user-submitted question or answer content.

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

Upgrade to phpMyFAQ 4.1.2 or later; alternatively, remove or replace the raw Twig filter usage on user-submitted content and implement proper output encoding to prevent encode-decode bypass.

Recommended fix Moderate confidence

phpMyFAQ 4.1.2 or later

  1. 1. Backup your current phpMyFAQ installation and database before proceeding with any upgrade.
  2. 2. Download phpMyFAQ version 4.1.2 or later from the official repository (github.com/thorsten/phpMyFAQ).
  3. 3. Replace the existing phpMyFAQ files with the new version, preserving your configuration and database connection settings.
  4. 4. Verify the upgrade was successful by logging into the admin panel.
  5. 5. Test FAQ creation and update functionality to confirm the XSS vulnerability is remediated.
  6. 6. Ensure that any custom Twig templates using the raw filter are reviewed for proper sanitization before use.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46363 — 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-46363 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