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

CVE-2026-46367

HIGH · 7.6 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 →
80/100
Remediation priority · High
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 Utils::parseUrl() that allows authenticated users to inject JavaScript via malformed URLs in comments. Attackers can craft URLs with unescaped quotes to inject event handlers, stealing admin session cookies and achieving full application takeover when visitors view affected FAQ pages.

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 the Utils::parseUrl() function where URLs in comments are not properly escaped, allowing injection of event handlers via unescaped quotes. Authenticated users can craft malicious URLs that execute JavaScript when visitors view affected FAQ pages, enabling session cookie theft and full application takeover.

MitigationUpgrade to phpMyFAQ 4.1.2 or later which contains the fix for proper quote escaping in Utils::parseUrl(). Alternatively, implement input validation to sanitize URLs in comments before storage.

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
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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
    Locate the version file or check the footer/admin panel for the installed phpMyFAQ version number
    Affected if The installed version is below 4.1.2 (e.g., 4.1.1, 4.0.x, 3.x)
  2. Confirm comments feature is enabled
    Check the phpMyFAQ configuration file (usually inc/PMF/Configuration.php or config/database.php) for the 'comments.enable' setting or review the admin settings page
    Affected if The comments feature is enabled, allowing users to submit comments with URLs
  3. Verify if comment submission requires authentication
    Review the user registration and comment posting settings in the admin panel under 'Configuration' -> 'Security' or directly in the database table for settings
    Affected if Authenticated users (any registered user) can post comments, as the flaw requires an authenticated user to inject the malicious URL
  4. Inspect the Utils::parseUrl() function for escaping
    Locate the file containing Utils::parseUrl() (typically in src/PMF/Utils.php or similar) and check if the function uses htmlspecialchars() or equivalent escaping on URL parameters before output
    Affected if The function does NOT escape quotes or HTML entities in URLs before they are rendered in comments, leaving injection points for event handlers like onclick or onerror

You are affected if your phpMyFAQ version is below 4.1.2 AND the comments feature is enabled AND users can submit comments with URLs that are rendered without proper HTML escaping in the Utils::parseUrl() function.

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 which contains the fix for proper quote escaping in Utils::parseUrl(). Alternatively, implement input validation to sanitize URLs in comments before storage.

Recommended fix High confidence

phpMyFAQ 4.1.2

  1. Backup the existing phpMyFAQ database and all files
  2. Download phpMyFAQ version 4.1.2 from the official repository (github.com/phpmyfaq/phpmyfaq)
  3. Replace all existing phpMyFAQ files with the new version 4.1.2 files
  4. Run any database migration scripts included in the upgrade
  5. Verify the installation by logging in and checking the admin dashboard
  6. Clear all server-side caches to ensure the vulnerable code is not cached
  7. Test that legitimate URLs in comments are properly escaped after the upgrade
Caveat Review the changelog between your current version and 4.1.2 for any deprecated features or configuration changes before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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