CVE-2026-46360
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 · uneditedphpMyFAQ before 4.1.2 contains a stored cross-site scripting vulnerability in SvgSanitizer::decodeAllEntities() that limits recursive entity decoding to 5 iterations, allowing attackers to bypass sanitization. Authenticated users with FAQ_EDIT permission can upload malicious SVG files with deeply nested ampersand encoding around numeric HTML entities to reconstruct javascript: URLs, which execute arbitrary JavaScript when clicked by other users viewing the uploaded SVG.
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 · moderate confidencephpMyFAQ before 4.1.2 has a stored XSS vulnerability in the SvgSanitizer::decodeAllEntities() function. The sanitizer limits recursive entity decoding to 5 iterations, which can be bypassed using deeply nested ampersand encodings around numeric HTML entities to reconstruct javascript: URLs. Authenticated users with FAQ_EDIT permission can upload malicious SVG files that execute arbitrary JavaScript when viewed by other users.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify phpMyFAQ versionLocate the version file or admin dashboard that displays the installed phpMyFAQ version (typically in a version.php file or About section)Affected if The installed version is before 4.1.2 (e.g., 4.1.1, 4.0.x, or earlier)
-
Verify SVG upload functionality is enabledCheck the phpMyFAQ configuration or admin settings to determine if SVG file uploads are permitted for users with FAQ_EDIT permissionAffected if SVG uploads are allowed in the configuration
-
Confirm FAQ_EDIT permission assignmentReview the user role or permission settings to see which authenticated users have the FAQ_EDIT capability that allows file uploadsAffected if Any user account has FAQ_EDIT permission enabled
-
Inspect uploaded SVG filesSearch the upload directory (typically /attachments/, /images/, or similar upload paths) for SVG files and examine their contents for nested entity encodings or javascript: URL patternsAffected if SVG files containing nested & encoding patterns around numeric entities (like &#&#& sequences) or reconstructed javascript: URLs are present
You are affected if phpMyFAQ version is before 4.1.2 AND SVG uploads are enabled for users with FAQ_EDIT permission, allowing malicious SVG files with bypassed entity decoding to be stored and executed when viewed.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to phpMyFAQ 4.1.2 or later. Additionally, implement strict Content Security Policy headers and restrict SVG file uploads to only trusted users.
phpMyFAQ 4.1.2 or later
- 1. Backup your current phpMyFAQ installation and database before upgrading.
- 2. Download phpMyFAQ version 4.1.2 or later from the official source (github.com/thorsten/phpMyFAQ).
- 3. Replace the existing phpMyFAQ files with the new version, preserving your configuration and data files.
- 4. Verify the SvgSanitizer.php file contains the fix for recursive entity decoding limits.
- 5. Test SVG file uploads in a staging environment to confirm the sanitization properly blocks malicious payloads.
- 6. Deploy the upgrade to production after successful testing.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46360 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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