How severe is CVE-2025-69200?

CVE-2025-69200 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-69200?

CVE-2025-69200 affects the following packages: thorsten/phpmyfaq (Packagist), thorsten/phpmyfaq (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2025-69200?

Update thorsten/phpmyfaq to 4.0.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-69200 is resolved across your whole dependency graph.

How do I detect CVE-2025-69200 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for thorsten/phpmyfaq. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2025-69200 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-69200?

O3 pinpoints whether CVE-2025-69200 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-69200 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-69200 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2025-69200?

CVE-2025-69200 is classified as CWE-202 (CWE-202). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2025-69200?

A Nuclei detection template exists for CVE-2025-69200, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2025-69200 published, and has it been updated?

CVE-2025-69200 was published on December 29, 2025 and was last updated on August 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

CVE-2025-69200

HIGHFix: thorsten/phpMyFAQ@b0e99ee

CVE-2025-69200 is a high-severity (CVSS 7.5) CWE-202 vulnerability in thorsten/phpmyfaq. O3 Security confirms whether CVE-2025-69200 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

phpMyFAQ has unauthenticated config backup download via /api/setup/backup

Also known asGHSA-9cg9-4h4f-j6fg

Published

Dec 29, 2025

Updated

Aug 5, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Real-World Exposure

2 pkgs affected

🐘thorsten/phpmyfaq🐘thorsten/phpmyfaq

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

phpMyFAQ is an open source FAQ web application. In versions prior to 4.0.16, an unauthenticated remote attacker can trigger generation of a configuration backup ZIP via POST /api/setup/backup and then download the generated ZIP from a web-accessible location. The ZIP contains sensitive configuration files (e.g., database.php with database credentials), leading to high-impact information disclosure and potential follow-on compromise. Version 4.0.16 fixes the issue.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`thorsten/phpmyfaq`	all versions	4.0.16
🐘Packagist	`thorsten/phpmyfaq`	≥ 4.1.0-alpha	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for thorsten/phpmyfaq. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update thorsten/phpmyfaq to 4.0.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-69200 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-69200 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-69200. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

phpMyFAQ is an open source FAQ web application. In versions prior to 4.0.16, an unauthenticated remote attacker can trigger generation of a configuration backup ZIP via `POST /api/setup/backup` and then download the generated ZIP from a web-accessible location. The ZIP contains sensitive configuration files (e.g., `database.php` with database credentials), leading to high-impact information disclosure and potential follow-on compromise. Version 4.0.16 fixes the issue.

O3 Security · Impact-Aware SCA

Is CVE-2025-69200 in your dependencies?

O3 detects CVE-2025-69200 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works