{"items":[{"id":"NVI-00005776","kind":"vulnerability","title":"phpMyFAQ: Ordinary Authenticated User Can Access Admin-Only API Endpoints Due to Insufficient Authorization Check in phpMyFAQ","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jrc5-w569-h7h5","CVE-2026-45009"],"plain_summary":"GitHub lists this reviewed advisory for thorsten/phpmyfaq, phpmyfaq/phpmyfaq. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-923a59b1f3b584bcffde95530c8c9bc1"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.1.2 for thorsten/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-9c42cea15619555b7b7598e141f88823"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.1.2 for phpmyfaq/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-9c42cea15619555b7b7598e141f88823"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-09T00:01:49.000Z","value":"4.3 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-30706c473f51462af40e486a17a0ec37"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.211%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.11292. Missing scores are unknown.","source_id":"sr-923a59b1f3b584bcffde95530c8c9bc1"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-30706c473f51462af40e486a17a0ec37","url":"https://github.com/advisories/GHSA-jrc5-w569-h7h5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jrc5-w569-h7h5","publisher":"GitHub Advisory Database","observed_at":"2026-11-06T20:58:31.464Z"},{"id":"sr-9c42cea15619555b7b7598e141f88823","url":"https://github.com/advisories/GHSA-jrc5-w569-h7h5","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jrc5-w569-h7h5","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.969Z"},{"id":"sr-923a59b1f3b584bcffde95530c8c9bc1","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-45009","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-30706c473f51462af40e486a17a0ec37"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\n\nA review of `phpMyFAQ-main` uncovered an authorization issue in the `admin-api` routes.\n\nSeveral backend endpoints only check whether the caller is logged in. They do not verify that the caller actually has backend or administrative privileges. As a result, a normal frontend user can access API endpoints that are clearly intended for administrative use.\n\nDuring local reproduction, a regular user account was able to request `/admin/api/index.php/dashboard/versions` and receive a successful response from the backend management API.\n\nThis issue does not appear to give direct write access in the affected paths that were confirmed, so it should be treated as a backend information disclosure and privilege boundary failure rather than full admin compromise.\n\n### Details\n\nThe access control split is visible in the controller base class:\n\n```php\npublic function userIsAuthenticated(): void\n{\n    if (!$this->currentUser->isLoggedIn()) {\n        throw new UnauthorizedHttpException('Unauthorized access.');\n    }\n}\n\nprotected function userHasPermission(PermissionType $permissionType): void\n{\n    // permission-based check\n}\n```\n\nThe problem is that several `Administration\\Api` contro","public_affected_ranges":["= 4.1.1"]},{"certainty":"source_listed","source_ids":["sr-30706c473f51462af40e486a17a0ec37"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\n\nA review of `phpMyFAQ-main` uncovered an authorization issue in the `admin-api` routes.\n\nSeveral backend endpoints only check whether the caller is logged in. They do not verify that the caller actually has backend or administrative privileges. As a result, a normal frontend user can access API endpoints that are clearly intended for administrative use.\n\nDuring local reproduction, a regular user account was able to request `/admin/api/index.php/dashboard/versions` and receive a successful response from the backend management API.\n\nThis issue does not appear to give direct write access in the affected paths that were confirmed, so it should be treated as a backend information disclosure and privilege boundary failure rather than full admin compromise.\n\n### Details\n\nThe access control split is visible in the controller base class:\n\n```php\npublic function userIsAuthenticated(): void\n{\n    if (!$this->currentUser->isLoggedIn()) {\n        throw new UnauthorizedHttpException('Unauthorized access.');\n    }\n}\n\nprotected function userHasPermission(PermissionType $permissionType): void\n{\n    // permission-based check\n}\n```\n\nThe problem is that several `Administration\\Api` contro","public_affected_ranges":["= 4.1.1"]},{"certainty":"source_listed","source_ids":["sr-9c42cea15619555b7b7598e141f88823"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\n\nA review of `phpMyFAQ-main` uncovered an authorization issue in the `admin-api` routes.\n\nSeveral backend endpoints only check whether the caller is logged in. They do not verify that the caller actually has backend or administrative privileges. As a result, a normal frontend user can access API endpoints that are clearly intended for administrative use.\n\nDuring local reproduction, a regular user account was able to request `/admin/api/index.php/dashboard/versions` and receive a successful response from the backend management API.\n\nThis issue does not appear to give direct write access in the affected paths that were confirmed, so it should be treated as a backend information disclosure and privilege boundary failure rather than full admin compromise.\n\n### Details\n\nThe access control split is visible in the controller base class:\n\n```php\npublic function userIsAuthenticated(): void\n{\n    if (!$this->currentUser->isLoggedIn()) {\n        throw new UnauthorizedHttpException('Unauthorized access.');\n    }\n}\n\nprotected function userHasPermission(PermissionType $permissionType): void\n{\n    // permission-based check\n}\n```\n\nThe problem is that several `Administration\\Api` contro","public_affected_ranges":["ECOSYSTEM: introduced 4.1.1; fixed 4.1.2"]},{"certainty":"source_listed","source_ids":["sr-9c42cea15619555b7b7598e141f88823"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\n\nA review of `phpMyFAQ-main` uncovered an authorization issue in the `admin-api` routes.\n\nSeveral backend endpoints only check whether the caller is logged in. They do not verify that the caller actually has backend or administrative privileges. As a result, a normal frontend user can access API endpoints that are clearly intended for administrative use.\n\nDuring local reproduction, a regular user account was able to request `/admin/api/index.php/dashboard/versions` and receive a successful response from the backend management API.\n\nThis issue does not appear to give direct write access in the affected paths that were confirmed, so it should be treated as a backend information disclosure and privilege boundary failure rather than full admin compromise.\n\n### Details\n\nThe access control split is visible in the controller base class:\n\n```php\npublic function userIsAuthenticated(): void\n{\n    if (!$this->currentUser->isLoggedIn()) {\n        throw new UnauthorizedHttpException('Unauthorized access.');\n    }\n}\n\nprotected function userHasPermission(PermissionType $permissionType): void\n{\n    // permission-based check\n}\n```\n\nThe problem is that several `Administration\\Api` contro","public_affected_ranges":["ECOSYSTEM: introduced 4.1.1; fixed 4.1.2"]}],"null_published_at":"2026-11-07T07:07:39.842Z","source_updated_at":"2026-06-09T00:01:49.000Z","source_disclosed_at":"2026-05-06T20:37:42.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:30.969Z"},{"id":"NVI-00005776","kind":"vulnerability","title":"phpMyFAQ: Ordinary Authenticated User Can Access Admin-Only API Endpoints Due to Insufficient Authorization Check in phpMyFAQ","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jrc5-w569-h7h5","CVE-2026-45009"],"plain_summary":"OSV carries this publisher advisory for thorsten/phpmyfaq, phpmyfaq/phpmyfaq. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 4.1.2 for thorsten/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-9c42cea15619555b7b7598e141f88823"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.1.2 for phpmyfaq/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-9c42cea15619555b7b7598e141f88823"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-923a59b1f3b584bcffde95530c8c9bc1"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.211%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.11292. Missing scores are unknown.","source_id":"sr-923a59b1f3b584bcffde95530c8c9bc1"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-9c42cea15619555b7b7598e141f88823","url":"https://github.com/advisories/GHSA-jrc5-w569-h7h5","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jrc5-w569-h7h5","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.969Z"},{"id":"sr-923a59b1f3b584bcffde95530c8c9bc1","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-45009","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-9c42cea15619555b7b7598e141f88823"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\n\nA review of `phpMyFAQ-main` uncovered an authorization issue in the `admin-api` routes.\n\nSeveral backend endpoints only check whether the caller is logged in. They do not verify that the caller actually has backend or administrative privileges. As a result, a normal frontend user can access API endpoints that are clearly intended for administrative use.\n\nDuring local reproduction, a regular user account was able to request `/admin/api/index.php/dashboard/versions` and receive a successful response from the backend management API.\n\nThis issue does not appear to give direct write access in the affected paths that were confirmed, so it should be treated as a backend information disclosure and privilege boundary failure rather than full admin compromise.\n\n### Details\n\nThe access control split is visible in the controller base class:\n\n```php\npublic function userIsAuthenticated(): void\n{\n    if (!$this->currentUser->isLoggedIn()) {\n        throw new UnauthorizedHttpException('Unauthorized access.');\n    }\n}\n\nprotected function userHasPermission(PermissionType $permissionType): void\n{\n    // permission-based check\n}\n```\n\nThe problem is that several `Administration\\Api` contro","public_affected_ranges":["ECOSYSTEM: introduced 4.1.1; fixed 4.1.2"]},{"certainty":"source_listed","source_ids":["sr-9c42cea15619555b7b7598e141f88823"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\n\nA review of `phpMyFAQ-main` uncovered an authorization issue in the `admin-api` routes.\n\nSeveral backend endpoints only check whether the caller is logged in. They do not verify that the caller actually has backend or administrative privileges. As a result, a normal frontend user can access API endpoints that are clearly intended for administrative use.\n\nDuring local reproduction, a regular user account was able to request `/admin/api/index.php/dashboard/versions` and receive a successful response from the backend management API.\n\nThis issue does not appear to give direct write access in the affected paths that were confirmed, so it should be treated as a backend information disclosure and privilege boundary failure rather than full admin compromise.\n\n### Details\n\nThe access control split is visible in the controller base class:\n\n```php\npublic function userIsAuthenticated(): void\n{\n    if (!$this->currentUser->isLoggedIn()) {\n        throw new UnauthorizedHttpException('Unauthorized access.');\n    }\n}\n\nprotected function userHasPermission(PermissionType $permissionType): void\n{\n    // permission-based check\n}\n```\n\nThe problem is that several `Administration\\Api` contro","public_affected_ranges":["ECOSYSTEM: introduced 4.1.1; fixed 4.1.2"]}],"null_published_at":"2026-11-03T02:33:09.152Z","source_updated_at":"2026-09-10T03:51:06.198Z","source_disclosed_at":"2026-05-06T20:37:42.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:30.969Z"},{"id":"NVI-00005776","kind":"vulnerability","title":"phpMyFAQ: Ordinary Authenticated User Can Access Admin-Only API Endpoints Due to Insufficient Authorization Check in phpMyFAQ","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jrc5-w569-h7h5","CVE-2026-45009"],"plain_summary":"OSV carries this publisher advisory for thorsten/phpmyfaq, phpmyfaq/phpmyfaq. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 4.1.2 for thorsten/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-9c42cea15619555b7b7598e141f88823"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.1.2 for phpmyfaq/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-9c42cea15619555b7b7598e141f88823"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-9c42cea15619555b7b7598e141f88823","url":"https://github.com/advisories/GHSA-jrc5-w569-h7h5","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jrc5-w569-h7h5","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.969Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-9c42cea15619555b7b7598e141f88823"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\n\nA review of `phpMyFAQ-main` uncovered an authorization issue in the `admin-api` routes.\n\nSeveral backend endpoints only check whether the caller is logged in. They do not verify that the caller actually has backend or administrative privileges. As a result, a normal frontend user can access API endpoints that are clearly intended for administrative use.\n\nDuring local reproduction, a regular user account was able to request `/admin/api/index.php/dashboard/versions` and receive a successful response from the backend management API.\n\nThis issue does not appear to give direct write access in the affected paths that were confirmed, so it should be treated as a backend information disclosure and privilege boundary failure rather than full admin compromise.\n\n### Details\n\nThe access control split is visible in the controller base class:\n\n```php\npublic function userIsAuthenticated(): void\n{\n    if (!$this->currentUser->isLoggedIn()) {\n        throw new UnauthorizedHttpException('Unauthorized access.');\n    }\n}\n\nprotected function userHasPermission(PermissionType $permissionType): void\n{\n    // permission-based check\n}\n```\n\nThe problem is that several `Administration\\Api` contro","public_affected_ranges":["ECOSYSTEM: introduced 4.1.1; fixed 4.1.2"]},{"certainty":"source_listed","source_ids":["sr-9c42cea15619555b7b7598e141f88823"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\n\nA review of `phpMyFAQ-main` uncovered an authorization issue in the `admin-api` routes.\n\nSeveral backend endpoints only check whether the caller is logged in. They do not verify that the caller actually has backend or administrative privileges. As a result, a normal frontend user can access API endpoints that are clearly intended for administrative use.\n\nDuring local reproduction, a regular user account was able to request `/admin/api/index.php/dashboard/versions` and receive a successful response from the backend management API.\n\nThis issue does not appear to give direct write access in the affected paths that were confirmed, so it should be treated as a backend information disclosure and privilege boundary failure rather than full admin compromise.\n\n### Details\n\nThe access control split is visible in the controller base class:\n\n```php\npublic function userIsAuthenticated(): void\n{\n    if (!$this->currentUser->isLoggedIn()) {\n        throw new UnauthorizedHttpException('Unauthorized access.');\n    }\n}\n\nprotected function userHasPermission(PermissionType $permissionType): void\n{\n    // permission-based check\n}\n```\n\nThe problem is that several `Administration\\Api` contro","public_affected_ranges":["ECOSYSTEM: introduced 4.1.1; fixed 4.1.2"]}],"null_published_at":"2026-10-31T22:13:05.838Z","source_updated_at":"2026-09-10T03:51:06.198Z","source_disclosed_at":"2026-05-06T20:37:42.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:30.969Z"}],"next_cursor":null,"snapshot_revision":"42594"}