Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-88g4-74f3-63x9

phpMyFAQ has Potential Authenticated Path Traversal in PDF Export

CVSS 5.1 MediumEPSS 0.0040 · 34th percentile

Published by the GitHub Advisory Database at 25 Aug 2026, 17:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
thorsten/phpmyfaqPackagist>=4.0.0-alpha, <4.1.54.1.5
phpmyfaq/phpmyfaqPackagist>=4.0.0-alpha, <4.1.54.1.5
Identifiers
GHSA-88g4-74f3-63x9 · CVE-2026-57961 · PKSA-wjc4-72dv-h8tm · PKSA-wqvs-f8jk-pt53
Weakness (CWE)
CWE-22
Tags
Published
25 Aug 2026
Updated
26 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The phpMyFAQ packages thorsten/phpmyfaq and phpmyfaq/phpmyfaq, versions from 4.0.0-alpha before 4.1.5, have a path traversal flaw in PDF export image handling. A user with FAQ editing privileges could store HTML with crafted image paths, which may cause the application to attempt reading files outside the content directory and possibly expose them in the generated PDF. Upgrade to 4.1.5. The source gives few details on exploitability beyond code review.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.1 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0040, the 34th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.