{"items":[{"id":"NVI-00002310","kind":"vulnerability","title":"phpMyFAQ has SQL Injection in CurrentUser::setTokenData through unescaped OAuth token fields","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-pm8c-3qq3-72w7","CVE-2026-46359"],"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-133c15437f88d24a3a86ee74ed0dfd80"],"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-133c15437f88d24a3a86ee74ed0dfd80"],"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-6e5851b4d7308a5641b7f8d1b659521a"],"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":"CVSS","as_of":"2026-10-26T14:10:00.130Z","value":"7.5 HIGH (3.1)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-5da4b5bc7b5581c26f51958b87f3090c"},{"kind":"CVSS","as_of":"2026-10-26T14:10:00.130Z","value":"7.7 HIGH (4.0)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-5da4b5bc7b5581c26f51958b87f3090c"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.264%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.18357. Missing scores are unknown.","source_id":"sr-6e5851b4d7308a5641b7f8d1b659521a"}],"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-133c15437f88d24a3a86ee74ed0dfd80","url":"https://github.com/advisories/GHSA-pm8c-3qq3-72w7","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-pm8c-3qq3-72w7","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.992Z"},{"id":"sr-5da4b5bc7b5581c26f51958b87f3090c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46359","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-46359","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:11.754Z"},{"id":"sr-6e5851b4d7308a5641b7f8d1b659521a","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-46359","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-133c15437f88d24a3a86ee74ed0dfd80"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"## Summary\n\n`CurrentUser::setTokenData()` in `phpmyfaq/src/phpMyFAQ/User/CurrentUser.php` at lines 515-534 builds a SQL UPDATE statement with `sprintf` and interpolates OAuth token fields (`refresh_token`, `access_token`, `code_verifier`, and `json_encode($token['jwt'])`) without calling `$db->escape()`. Sibling methods `setAuthSource()` and `setRememberMe()` in the same file do call `$db->escape()` on user-controlled values, so the omission is local to this method. An attacker (Bob) whose Azure AD display name contains a single quote (for example `O'Brien`, or a deliberate SQL payload) breaks out of the string literal and injects arbitrary SQL against the phpMyFAQ database.\n\n## Details\n\n**Vulnerable code** (`phpmyfaq/src/phpMyFAQ/User/CurrentUser.php`, lines 513-534):\n\n```php\npublic function setTokenData(#[\\SensitiveParameter] array $token): bool\n{\n    $update = sprintf(\n        \"\n        UPDATE\n            %sfaquser\n        SET\n            refresh_token = '%s',\n            access_token = '%s',\n            code_verifier = '%s',\n            jwt = '%s'\n        WHERE\n            user_id = %d\",\n        Database::getTablePrefix(),\n        $token['refresh_token'],\n        $token['access","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.2"]},{"certainty":"source_listed","source_ids":["sr-133c15437f88d24a3a86ee74ed0dfd80"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"## Summary\n\n`CurrentUser::setTokenData()` in `phpmyfaq/src/phpMyFAQ/User/CurrentUser.php` at lines 515-534 builds a SQL UPDATE statement with `sprintf` and interpolates OAuth token fields (`refresh_token`, `access_token`, `code_verifier`, and `json_encode($token['jwt'])`) without calling `$db->escape()`. Sibling methods `setAuthSource()` and `setRememberMe()` in the same file do call `$db->escape()` on user-controlled values, so the omission is local to this method. An attacker (Bob) whose Azure AD display name contains a single quote (for example `O'Brien`, or a deliberate SQL payload) breaks out of the string literal and injects arbitrary SQL against the phpMyFAQ database.\n\n## Details\n\n**Vulnerable code** (`phpmyfaq/src/phpMyFAQ/User/CurrentUser.php`, lines 513-534):\n\n```php\npublic function setTokenData(#[\\SensitiveParameter] array $token): bool\n{\n    $update = sprintf(\n        \"\n        UPDATE\n            %sfaquser\n        SET\n            refresh_token = '%s',\n            access_token = '%s',\n            code_verifier = '%s',\n            jwt = '%s'\n        WHERE\n            user_id = %d\",\n        Database::getTablePrefix(),\n        $token['refresh_token'],\n        $token['access","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.2"]}],"null_published_at":"2026-11-02T20:21:10.274Z","source_updated_at":"2026-09-10T03:51:06.733Z","source_disclosed_at":"2026-05-06T20:44:39.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.992Z"},{"id":"NVI-00002310","kind":"vulnerability","title":"phpMyFAQ has SQL Injection in CurrentUser::setTokenData through unescaped OAuth token fields","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pm8c-3qq3-72w7","CVE-2026-46359"],"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-133c15437f88d24a3a86ee74ed0dfd80"],"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-133c15437f88d24a3a86ee74ed0dfd80"],"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-6e5851b4d7308a5641b7f8d1b659521a"],"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.264%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.18357. Missing scores are unknown.","source_id":"sr-6e5851b4d7308a5641b7f8d1b659521a"}],"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-133c15437f88d24a3a86ee74ed0dfd80","url":"https://github.com/advisories/GHSA-pm8c-3qq3-72w7","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-pm8c-3qq3-72w7","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.992Z"},{"id":"sr-6e5851b4d7308a5641b7f8d1b659521a","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-46359","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-133c15437f88d24a3a86ee74ed0dfd80"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"## Summary\n\n`CurrentUser::setTokenData()` in `phpmyfaq/src/phpMyFAQ/User/CurrentUser.php` at lines 515-534 builds a SQL UPDATE statement with `sprintf` and interpolates OAuth token fields (`refresh_token`, `access_token`, `code_verifier`, and `json_encode($token['jwt'])`) without calling `$db->escape()`. Sibling methods `setAuthSource()` and `setRememberMe()` in the same file do call `$db->escape()` on user-controlled values, so the omission is local to this method. An attacker (Bob) whose Azure AD display name contains a single quote (for example `O'Brien`, or a deliberate SQL payload) breaks out of the string literal and injects arbitrary SQL against the phpMyFAQ database.\n\n## Details\n\n**Vulnerable code** (`phpmyfaq/src/phpMyFAQ/User/CurrentUser.php`, lines 513-534):\n\n```php\npublic function setTokenData(#[\\SensitiveParameter] array $token): bool\n{\n    $update = sprintf(\n        \"\n        UPDATE\n            %sfaquser\n        SET\n            refresh_token = '%s',\n            access_token = '%s',\n            code_verifier = '%s',\n            jwt = '%s'\n        WHERE\n            user_id = %d\",\n        Database::getTablePrefix(),\n        $token['refresh_token'],\n        $token['access","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.2"]},{"certainty":"source_listed","source_ids":["sr-133c15437f88d24a3a86ee74ed0dfd80"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"## Summary\n\n`CurrentUser::setTokenData()` in `phpmyfaq/src/phpMyFAQ/User/CurrentUser.php` at lines 515-534 builds a SQL UPDATE statement with `sprintf` and interpolates OAuth token fields (`refresh_token`, `access_token`, `code_verifier`, and `json_encode($token['jwt'])`) without calling `$db->escape()`. Sibling methods `setAuthSource()` and `setRememberMe()` in the same file do call `$db->escape()` on user-controlled values, so the omission is local to this method. An attacker (Bob) whose Azure AD display name contains a single quote (for example `O'Brien`, or a deliberate SQL payload) breaks out of the string literal and injects arbitrary SQL against the phpMyFAQ database.\n\n## Details\n\n**Vulnerable code** (`phpmyfaq/src/phpMyFAQ/User/CurrentUser.php`, lines 513-534):\n\n```php\npublic function setTokenData(#[\\SensitiveParameter] array $token): bool\n{\n    $update = sprintf(\n        \"\n        UPDATE\n            %sfaquser\n        SET\n            refresh_token = '%s',\n            access_token = '%s',\n            code_verifier = '%s',\n            jwt = '%s'\n        WHERE\n            user_id = %d\",\n        Database::getTablePrefix(),\n        $token['refresh_token'],\n        $token['access","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.2"]}],"null_published_at":"2026-11-01T19:14:01.578Z","source_updated_at":"2026-09-10T03:51:06.733Z","source_disclosed_at":"2026-05-06T20:44:39.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.992Z"},{"id":"NVI-00002310","kind":"vulnerability","title":"phpMyFAQ has SQL Injection in CurrentUser::setTokenData through unescaped OAuth token fields","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pm8c-3qq3-72w7","CVE-2026-46359"],"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-133c15437f88d24a3a86ee74ed0dfd80"],"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-133c15437f88d24a3a86ee74ed0dfd80"],"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-133c15437f88d24a3a86ee74ed0dfd80","url":"https://github.com/advisories/GHSA-pm8c-3qq3-72w7","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-pm8c-3qq3-72w7","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.992Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-133c15437f88d24a3a86ee74ed0dfd80"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"## Summary\n\n`CurrentUser::setTokenData()` in `phpmyfaq/src/phpMyFAQ/User/CurrentUser.php` at lines 515-534 builds a SQL UPDATE statement with `sprintf` and interpolates OAuth token fields (`refresh_token`, `access_token`, `code_verifier`, and `json_encode($token['jwt'])`) without calling `$db->escape()`. Sibling methods `setAuthSource()` and `setRememberMe()` in the same file do call `$db->escape()` on user-controlled values, so the omission is local to this method. An attacker (Bob) whose Azure AD display name contains a single quote (for example `O'Brien`, or a deliberate SQL payload) breaks out of the string literal and injects arbitrary SQL against the phpMyFAQ database.\n\n## Details\n\n**Vulnerable code** (`phpmyfaq/src/phpMyFAQ/User/CurrentUser.php`, lines 513-534):\n\n```php\npublic function setTokenData(#[\\SensitiveParameter] array $token): bool\n{\n    $update = sprintf(\n        \"\n        UPDATE\n            %sfaquser\n        SET\n            refresh_token = '%s',\n            access_token = '%s',\n            code_verifier = '%s',\n            jwt = '%s'\n        WHERE\n            user_id = %d\",\n        Database::getTablePrefix(),\n        $token['refresh_token'],\n        $token['access","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.2"]},{"certainty":"source_listed","source_ids":["sr-133c15437f88d24a3a86ee74ed0dfd80"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"## Summary\n\n`CurrentUser::setTokenData()` in `phpmyfaq/src/phpMyFAQ/User/CurrentUser.php` at lines 515-534 builds a SQL UPDATE statement with `sprintf` and interpolates OAuth token fields (`refresh_token`, `access_token`, `code_verifier`, and `json_encode($token['jwt'])`) without calling `$db->escape()`. Sibling methods `setAuthSource()` and `setRememberMe()` in the same file do call `$db->escape()` on user-controlled values, so the omission is local to this method. An attacker (Bob) whose Azure AD display name contains a single quote (for example `O'Brien`, or a deliberate SQL payload) breaks out of the string literal and injects arbitrary SQL against the phpMyFAQ database.\n\n## Details\n\n**Vulnerable code** (`phpmyfaq/src/phpMyFAQ/User/CurrentUser.php`, lines 513-534):\n\n```php\npublic function setTokenData(#[\\SensitiveParameter] array $token): bool\n{\n    $update = sprintf(\n        \"\n        UPDATE\n            %sfaquser\n        SET\n            refresh_token = '%s',\n            access_token = '%s',\n            code_verifier = '%s',\n            jwt = '%s'\n        WHERE\n            user_id = %d\",\n        Database::getTablePrefix(),\n        $token['refresh_token'],\n        $token['access","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.2"]}],"null_published_at":"2026-10-31T22:00:33.874Z","source_updated_at":"2026-09-10T03:51:06.733Z","source_disclosed_at":"2026-05-06T20:44:39.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.992Z"}],"next_cursor":null,"snapshot_revision":"42594"}