CVE-2026-49205

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

phpMyFAQ is an open source FAQ web application. Versions prior to 4.1.4 have Missing Authorization in the API CategoryController. CVE-2026-24421 addressed this in the BackupController by adding: $this->userHasPermission(PermissionType::BACKUP). The same fix was not applied to 4 other write endpoints in the public API. All 4 only call $this->hasValidToken() — which checks a shared API key header, rather than the individual user's role permissions. The following APIs are affected: POST /api/v4.0/category (CategoryController::create), POST /api/v4.0/faq (FaqController::create), PUT /api/v4.0/faq (FaqController::update), and POST /api/v4.0/question (QuestionController::create). This issue has been fixed in version 4.1.4.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

June 18, 2026

Last Modified

June 23, 2026

Advisory Details (2)

Auto-updated Jun 18, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Incomplete fix for CVE-2026-24421: Missing userHasPermission() in 4 API write endpoints · Advisory · thorsten/phpMyFAQ · GitHub

https://github.com/thorsten/phpMyFAQ/security/advisories/GHSA-8c6h-7g6x-m5x4
github_commit Patch Available

commit d5c195b1ecf5 (thorsten/phpMyFAQ)

Patch available: thorsten/phpMyFAQ 4.1-nightly-2026-06-03 (contains commit d5c195b1ecf5)

https://github.com/thorsten/phpMyFAQ/commit/d5c195b1ecf5dc30fb825d7eb50d22481c24cb07

Vendor Advisories for CVE-2026-49205(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFixed inDependents
phpmyfaq/phpmyfaq2.10.0-alpha ... 4.1.3 (172 versions)4.1.4—
thorsten/phpmyfaq2.10.0-alpha ... 4.1.3 (172 versions)4.1.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 00:46 UTCEG score recompute
  3. 2026-08-23 01:03 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 07:54 UTCEG score recompute
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 08:08 UTCEG score recompute
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 07:25 UTCEG score recompute
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 08:34 UTCEG score recompute
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 08:49 UTCEG score recompute
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 09:03 UTCEG score recompute
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 07:35 UTCEG score recompute
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 07:49 UTCEG score recompute
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-12 07:13 UTCEG score recompute
  24. 2026-08-11 07:27 UTCEG score recompute
  25. 2026-08-11 00:00 UTCEPSS rescore
Show 64 more
  1. 2026-08-10 07:42 UTCEG score recompute
  2. 2026-08-09 13:46 UTCEPSS rescore
  3. 2026-08-09 07:55 UTCEG score recompute
  4. 2026-08-08 16:37 UTCEPSS rescore
  5. 2026-08-08 08:10 UTCEG score recompute
  6. 2026-08-07 08:24 UTCEG score recompute
  7. 2026-08-06 13:47 UTCEPSS rescore
  8. 2026-08-06 08:38 UTCEG score recompute
  9. 2026-08-05 19:17 UTCEPSS rescore
  10. 2026-08-05 08:52 UTCEG score recompute
  11. 2026-08-04 15:10 UTCEPSS rescore
  12. 2026-08-04 10:39 UTCEPSS rescore
  13. 2026-08-04 04:25 UTCEG score recompute
  14. 2026-08-03 10:36 UTCEPSS rescore
  15. 2026-08-02 04:53 UTCEG score recompute
  16. 2026-08-02 02:27 UTCEPSS rescore
  17. 2026-08-01 05:07 UTCEG score recompute
  18. 2026-08-01 04:16 UTCEPSS rescore
  19. 2026-07-31 03:50 UTCEG score recompute
  20. 2026-07-30 16:28 UTCEPSS rescore
  21. 2026-07-30 03:04 UTCEG score recompute
  22. 2026-07-30 01:30 UTCEPSS rescore
  23. 2026-07-29 01:43 UTCEG score recompute
  24. 2026-07-28 15:37 UTCEPSS rescore
  25. 2026-07-27 18:05 UTCEG score recompute
  26. 2026-07-26 17:17 UTCEG score recompute
  27. 2026-07-26 14:54 UTCEPSS rescore
  28. 2026-07-25 14:18 UTCEPSS rescore
  29. 2026-07-24 14:18 UTCEPSS rescore
  30. 2026-07-23 14:18 UTCEPSS rescore
  31. 2026-07-23 03:18 UTCEG score recompute
  32. 2026-07-22 14:08 UTCEPSS rescore
  33. 2026-07-21 15:25 UTCEPSS rescore
  34. 2026-07-20 17:08 UTCEPSS rescore
  35. 2026-07-19 02:29 UTCEPSS rescore
  36. 2026-07-18 10:04 UTCEPSS rescore
  37. 2026-07-16 17:03 UTCEPSS rescore
  38. 2026-07-15 16:57 UTCEPSS rescore
  39. 2026-07-15 02:00 UTCEPSS rescore
  40. 2026-07-13 22:30 UTCEPSS rescore
  41. 2026-07-13 06:13 UTCEPSS rescore
  42. 2026-07-12 05:46 UTCEPSS rescore
  43. 2026-07-11 08:27 UTCEPSS rescore
  44. 2026-07-09 19:10 UTCEPSS rescore
  45. 2026-07-08 15:16 UTCEPSS rescore
  46. 2026-07-07 13:46 UTCEPSS rescore
  47. 2026-07-06 16:27 UTCEPSS rescore
  48. 2026-07-06 02:23 UTCEPSS rescore
  49. 2026-07-05 02:30 UTCEPSS rescore
  50. 2026-07-04 06:31 UTCEPSS rescore
  51. 2026-07-01 15:07 UTCEPSS rescore
  52. 2026-06-30 23:22 UTCEPSS rescore
  53. 2026-06-29 14:06 UTCEPSS rescore
  54. 2026-06-29 14:06 UTCEPSS rescore
  55. 2026-06-28 14:07 UTCEPSS rescore
  56. 2026-06-28 04:56 UTCEPSS rescore
  57. 2026-06-28 04:56 UTCEPSS rescore
  58. 2026-06-27 03:08 UTCEPSS rescore
  59. 2026-06-25 13:49 UTCEPSS rescore
  60. 2026-06-24 14:05 UTCEPSS rescore
  61. 2026-06-23 21:33 UTCEPSS rescore
  62. 2026-06-23 21:33 UTCEPSS rescore
  63. 2026-06-18 23:24 UTCEG score recompute
  64. 2026-06-18 23:22 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49205?
CVE-2026-49205 is a medium vulnerability published on June 18, 2026. phpMyFAQ is an open source FAQ web application. Versions prior to 4.1.4 have Missing Authorization in the API CategoryController. CVE-2026-24421 addressed this in the BackupController by adding: $this->userHasPermission(PermissionType::BACKUP). The same fix was not applied to 4 other write…
When was CVE-2026-49205 disclosed?
CVE-2026-49205 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49205 actively exploited?
CVE-2026-49205 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.7% of all scored CVEs.
What is the CVSS score of CVE-2026-49205?
CVE-2026-49205 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-49205?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49205, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49205

Explore →

Is Your Infrastructure Affected by CVE-2026-49205?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs