Description
phpMyFAQ from 4.2.0-alpha before 4.2.0-beta contains a stored cross-site scripting vulnerability in SvgSanitizer that allows FAQ editors to store executable SVG files. Attackers can split script tags around removed tokens like processing instructions so single-pass removal reassembles them, executing script in the application origin when victims open the file.
Published: 2026-10-17
Score: 5.1 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Stored cross‑site scripting that allows executable SVG files to run scripts in the application origin
Action: Patch
AI Analysis

Impact

The bug is a stored XSS flaw in the SvgSanitizer component of phpMyFAQ. By uploading an SVG file that contains script elements whose tags are broken around characters that the sanitizer removes, the single‑pass sanitization reassembles the tags when the image is displayed, causing the embedded script to run in the context of the application. Attackers who can act as FAQ editors can thus store malicious SVG that will execute arbitrary JavaScript in any viewer’s browser.

Affected Systems

The issue affects the phpMyFAQ content‑management system from Thorsten. All releases from 4.2.0‑alpha up to but not including 4.2.0‑beta are vulnerable.

Risk and Exploitability

The CVSS score of 5.1 marks the flaw as a medium‑severity issue. No EPSS score is available and it is not listed in CISA’s KEV catalog, indicating a moderate probability of real‑world exploitation. The attacker needs editor privileges to upload a malicious file or must persuade a user to open the SVG. When the SVG is rendered, the injected script runs with the application origin, allowing in‑browser payload execution but not allowing arbitrary system access. The attack surface is thus limited to users who view the file, but the impact on confidentiality and integrity of the application session can be significant.

Generated by OpenCVE AI on October 17, 2026 at 20:51 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade phpMyFAQ to version 4.2.0‑beta or newer where the SvgSanitizer bug has been fixed.
  • Restrict SVG upload rights to trusted administrators only to prevent ordinary users from uploading potentially malicious files.
  • If an immediate upgrade is not possible, disable SVG uploads or enforce a stricter sanitization routine, and scan existing assets for embedded script tags to mitigate stored XSS risk.

Generated by OpenCVE AI on October 17, 2026 at 20:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 18 Oct 2026 21:30:00 +0000

Type Values Removed Values Added
First Time appeared Thorsten
Thorsten phpmyfaq
Vendors & Products Thorsten
Thorsten phpmyfaq

Sat, 17 Oct 2026 19:00:00 +0000

Type Values Removed Values Added
Description phpMyFAQ from 4.2.0-alpha before 4.2.0-beta contains a stored cross-site scripting vulnerability in SvgSanitizer that allows FAQ editors to store executable SVG files. Attackers can split script tags around removed tokens like processing instructions so single-pass removal reassembles them, executing script in the application origin when victims open the file.
Title phpMyFAQ 4.2.0-alpha before 4.2.0-beta Stored XSS via SVG Upload Sanitizer Bypass
First Time appeared Phpmyfaq
Phpmyfaq phpmyfaq
Weaknesses CWE-182
CPEs cpe:2.3:a:phpmyfaq:phpmyfaq:*:*:*:*:*:*:*:*
Vendors & Products Phpmyfaq
Phpmyfaq phpmyfaq
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N'}

cvssV4_0

{'score': 5.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N'}


Subscriptions

Phpmyfaq Phpmyfaq
Thorsten Phpmyfaq
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-10-17T18:46:19.253Z

Reserved: 2026-10-17T12:16:44.850Z

Link: CVE-2026-111896

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-10-17T19:16:31.337

Modified: 2026-10-17T19:16:31.447

Link: CVE-2026-111896

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-18T21:15:13Z

Weaknesses
  • CWE-182

    Collapse of Data into Unsafe Value