{"items":[{"id":"NVI-00004686","kind":"vulnerability","title":"phpMyFAQ: Missing Password Reset Token Allows Account Takeover via Username/Email Enumeration","revision":4,"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-w9xh-5f39-vq89","CVE-2026-35675"],"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-0c7649c86f6c79cfa1e2e6069c651230"],"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.3 for thorsten/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"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.3 for phpmyfaq/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"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-05-31T05:51:35.000Z","value":"8.2 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-350b05ade8ff89a70cad5ee19b69728e"},{"kind":"CVSS","as_of":"2026-10-26T13:10:00.140Z","value":"8.2 HIGH (3.1)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-9d295c3c0941be81be11cbe9566eeeb9"},{"kind":"CVSS","as_of":"2026-10-26T13:10:00.140Z","value":"8.8 HIGH (4.0)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-9d295c3c0941be81be11cbe9566eeeb9"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.417%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.35977. Missing scores are unknown.","source_id":"sr-0c7649c86f6c79cfa1e2e6069c651230"}],"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-350b05ade8ff89a70cad5ee19b69728e","url":"https://github.com/advisories/GHSA-w9xh-5f39-vq89","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-w9xh-5f39-vq89","publisher":"GitHub Advisory Database","observed_at":"2026-11-07T00:53:14.635Z"},{"id":"sr-6f7dfcd20ebaa48786265499dffa259a","url":"https://github.com/advisories/GHSA-w9xh-5f39-vq89","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-w9xh-5f39-vq89","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"},{"id":"sr-9d295c3c0941be81be11cbe9566eeeb9","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-35675","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-35675","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:23:52.242Z"},{"id":"sr-0c7649c86f6c79cfa1e2e6069c651230","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-35675","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.852Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-350b05ade8ff89a70cad5ee19b69728e"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nAn authentication bypass vulnerability in phpMyFAQ allows any unauthenticated attacker to reset the password of any user account, including SuperAdmin accounts. By sending a PUT request with just a valid username and associated email address to /api/user/password/update, an attacker receives a new plaintext password via email without any token verification, rate limiting, or email confirmation. This enables complete account takeover of any user, including full administrative access.\n\n\n### Details\nFile: phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/UnauthorizedUserController.php\nLines: 56-130\nThe updatePassword() method at line 56 accepts PUT requests to /user/password/update with only username and email in the JSON body:\n#[Route(path: 'user/password/update', name: 'api.private.user.password', methods: ['PUT'])]\n```php\npublic function updatePassword(Request $request): JsonResponse\n{\n    $data = json_decode($request->getContent());\n    $username = trim((string) Filter::filterVar($data->username, FILTER_SANITIZE_SPECIAL_CHARS));\n    $email = trim((string) Filter::filterEmail($data->email));\n    if ($username !== '' && $username !== '0' && ($email !== '' && $email !== '0'))","public_affected_ranges":["< 4.1.3"]},{"certainty":"source_listed","source_ids":["sr-350b05ade8ff89a70cad5ee19b69728e"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nAn authentication bypass vulnerability in phpMyFAQ allows any unauthenticated attacker to reset the password of any user account, including SuperAdmin accounts. By sending a PUT request with just a valid username and associated email address to /api/user/password/update, an attacker receives a new plaintext password via email without any token verification, rate limiting, or email confirmation. This enables complete account takeover of any user, including full administrative access.\n\n\n### Details\nFile: phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/UnauthorizedUserController.php\nLines: 56-130\nThe updatePassword() method at line 56 accepts PUT requests to /user/password/update with only username and email in the JSON body:\n#[Route(path: 'user/password/update', name: 'api.private.user.password', methods: ['PUT'])]\n```php\npublic function updatePassword(Request $request): JsonResponse\n{\n    $data = json_decode($request->getContent());\n    $username = trim((string) Filter::filterVar($data->username, FILTER_SANITIZE_SPECIAL_CHARS));\n    $email = trim((string) Filter::filterEmail($data->email));\n    if ($username !== '' && $username !== '0' && ($email !== '' && $email !== '0'))","public_affected_ranges":["< 4.1.3"]},{"certainty":"source_listed","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nAn authentication bypass vulnerability in phpMyFAQ allows any unauthenticated attacker to reset the password of any user account, including SuperAdmin accounts. By sending a PUT request with just a valid username and associated email address to /api/user/password/update, an attacker receives a new plaintext password via email without any token verification, rate limiting, or email confirmation. This enables complete account takeover of any user, including full administrative access.\n\n\n### Details\nFile: phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/UnauthorizedUserController.php\nLines: 56-130\nThe updatePassword() method at line 56 accepts PUT requests to /user/password/update with only username and email in the JSON body:\n#[Route(path: 'user/password/update', name: 'api.private.user.password', methods: ['PUT'])]\n```php\npublic function updatePassword(Request $request): JsonResponse\n{\n    $data = json_decode($request->getContent());\n    $username = trim((string) Filter::filterVar($data->username, FILTER_SANITIZE_SPECIAL_CHARS));\n    $email = trim((string) Filter::filterEmail($data->email));\n    if ($username !== '' && $username !== '0' && ($email !== '' && $email !== '0'))","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.3"]},{"certainty":"source_listed","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nAn authentication bypass vulnerability in phpMyFAQ allows any unauthenticated attacker to reset the password of any user account, including SuperAdmin accounts. By sending a PUT request with just a valid username and associated email address to /api/user/password/update, an attacker receives a new plaintext password via email without any token verification, rate limiting, or email confirmation. This enables complete account takeover of any user, including full administrative access.\n\n\n### Details\nFile: phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/UnauthorizedUserController.php\nLines: 56-130\nThe updatePassword() method at line 56 accepts PUT requests to /user/password/update with only username and email in the JSON body:\n#[Route(path: 'user/password/update', name: 'api.private.user.password', methods: ['PUT'])]\n```php\npublic function updatePassword(Request $request): JsonResponse\n{\n    $data = json_decode($request->getContent());\n    $username = trim((string) Filter::filterVar($data->username, FILTER_SANITIZE_SPECIAL_CHARS));\n    $email = trim((string) Filter::filterEmail($data->email));\n    if ($username !== '' && $username !== '0' && ($email !== '' && $email !== '0'))","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.3"]}],"null_published_at":"2026-11-07T07:07:39.846Z","source_updated_at":"2026-05-31T05:51:35.000Z","source_disclosed_at":"2026-05-20T15:46:55.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:41.386Z"},{"id":"NVI-00004686","kind":"vulnerability","title":"phpMyFAQ: Missing Password Reset Token Allows Account Takeover via Username/Email Enumeration","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-w9xh-5f39-vq89","CVE-2026-35675"],"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.3 for thorsten/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"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.3 for phpmyfaq/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"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-0c7649c86f6c79cfa1e2e6069c651230"],"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-26T13:10:00.140Z","value":"8.2 HIGH (3.1)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-9d295c3c0941be81be11cbe9566eeeb9"},{"kind":"CVSS","as_of":"2026-10-26T13:10:00.140Z","value":"8.8 HIGH (4.0)","meaning":"disclosure@vulncheck.com severity; no combined Null risk score.","source_id":"sr-9d295c3c0941be81be11cbe9566eeeb9"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.417%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.35977. Missing scores are unknown.","source_id":"sr-0c7649c86f6c79cfa1e2e6069c651230"}],"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-6f7dfcd20ebaa48786265499dffa259a","url":"https://github.com/advisories/GHSA-w9xh-5f39-vq89","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-w9xh-5f39-vq89","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"},{"id":"sr-9d295c3c0941be81be11cbe9566eeeb9","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-35675","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-35675","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:23:52.242Z"},{"id":"sr-0c7649c86f6c79cfa1e2e6069c651230","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-35675","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.852Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nAn authentication bypass vulnerability in phpMyFAQ allows any unauthenticated attacker to reset the password of any user account, including SuperAdmin accounts. By sending a PUT request with just a valid username and associated email address to /api/user/password/update, an attacker receives a new plaintext password via email without any token verification, rate limiting, or email confirmation. This enables complete account takeover of any user, including full administrative access.\n\n\n### Details\nFile: phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/UnauthorizedUserController.php\nLines: 56-130\nThe updatePassword() method at line 56 accepts PUT requests to /user/password/update with only username and email in the JSON body:\n#[Route(path: 'user/password/update', name: 'api.private.user.password', methods: ['PUT'])]\n```php\npublic function updatePassword(Request $request): JsonResponse\n{\n    $data = json_decode($request->getContent());\n    $username = trim((string) Filter::filterVar($data->username, FILTER_SANITIZE_SPECIAL_CHARS));\n    $email = trim((string) Filter::filterEmail($data->email));\n    if ($username !== '' && $username !== '0' && ($email !== '' && $email !== '0'))","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.3"]},{"certainty":"source_listed","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nAn authentication bypass vulnerability in phpMyFAQ allows any unauthenticated attacker to reset the password of any user account, including SuperAdmin accounts. By sending a PUT request with just a valid username and associated email address to /api/user/password/update, an attacker receives a new plaintext password via email without any token verification, rate limiting, or email confirmation. This enables complete account takeover of any user, including full administrative access.\n\n\n### Details\nFile: phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/UnauthorizedUserController.php\nLines: 56-130\nThe updatePassword() method at line 56 accepts PUT requests to /user/password/update with only username and email in the JSON body:\n#[Route(path: 'user/password/update', name: 'api.private.user.password', methods: ['PUT'])]\n```php\npublic function updatePassword(Request $request): JsonResponse\n{\n    $data = json_decode($request->getContent());\n    $username = trim((string) Filter::filterVar($data->username, FILTER_SANITIZE_SPECIAL_CHARS));\n    $email = trim((string) Filter::filterEmail($data->email));\n    if ($username !== '' && $username !== '0' && ($email !== '' && $email !== '0'))","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.3"]}],"null_published_at":"2026-11-06T15:18:11.513Z","source_updated_at":"2026-09-10T03:50:47.931Z","source_disclosed_at":"2026-05-20T15:46:55.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:41.386Z"},{"id":"NVI-00004686","kind":"vulnerability","title":"phpMyFAQ: Missing Password Reset Token Allows Account Takeover via Username/Email Enumeration","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-w9xh-5f39-vq89","CVE-2026-35675"],"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.3 for thorsten/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"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.3 for phpmyfaq/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"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-0c7649c86f6c79cfa1e2e6069c651230"],"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-11-02T12:00:30.000Z","value":"0.417%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.35977. Missing scores are unknown.","source_id":"sr-0c7649c86f6c79cfa1e2e6069c651230"}],"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-6f7dfcd20ebaa48786265499dffa259a","url":"https://github.com/advisories/GHSA-w9xh-5f39-vq89","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-w9xh-5f39-vq89","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"},{"id":"sr-0c7649c86f6c79cfa1e2e6069c651230","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-35675","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.852Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nAn authentication bypass vulnerability in phpMyFAQ allows any unauthenticated attacker to reset the password of any user account, including SuperAdmin accounts. By sending a PUT request with just a valid username and associated email address to /api/user/password/update, an attacker receives a new plaintext password via email without any token verification, rate limiting, or email confirmation. This enables complete account takeover of any user, including full administrative access.\n\n\n### Details\nFile: phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/UnauthorizedUserController.php\nLines: 56-130\nThe updatePassword() method at line 56 accepts PUT requests to /user/password/update with only username and email in the JSON body:\n#[Route(path: 'user/password/update', name: 'api.private.user.password', methods: ['PUT'])]\n```php\npublic function updatePassword(Request $request): JsonResponse\n{\n    $data = json_decode($request->getContent());\n    $username = trim((string) Filter::filterVar($data->username, FILTER_SANITIZE_SPECIAL_CHARS));\n    $email = trim((string) Filter::filterEmail($data->email));\n    if ($username !== '' && $username !== '0' && ($email !== '' && $email !== '0'))","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.3"]},{"certainty":"source_listed","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nAn authentication bypass vulnerability in phpMyFAQ allows any unauthenticated attacker to reset the password of any user account, including SuperAdmin accounts. By sending a PUT request with just a valid username and associated email address to /api/user/password/update, an attacker receives a new plaintext password via email without any token verification, rate limiting, or email confirmation. This enables complete account takeover of any user, including full administrative access.\n\n\n### Details\nFile: phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/UnauthorizedUserController.php\nLines: 56-130\nThe updatePassword() method at line 56 accepts PUT requests to /user/password/update with only username and email in the JSON body:\n#[Route(path: 'user/password/update', name: 'api.private.user.password', methods: ['PUT'])]\n```php\npublic function updatePassword(Request $request): JsonResponse\n{\n    $data = json_decode($request->getContent());\n    $username = trim((string) Filter::filterVar($data->username, FILTER_SANITIZE_SPECIAL_CHARS));\n    $email = trim((string) Filter::filterEmail($data->email));\n    if ($username !== '' && $username !== '0' && ($email !== '' && $email !== '0'))","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.3"]}],"null_published_at":"2026-11-04T10:04:47.587Z","source_updated_at":"2026-09-10T03:50:47.931Z","source_disclosed_at":"2026-05-20T15:46:55.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:41.386Z"},{"id":"NVI-00004686","kind":"vulnerability","title":"phpMyFAQ: Missing Password Reset Token Allows Account Takeover via Username/Email Enumeration","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-w9xh-5f39-vq89","CVE-2026-35675"],"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.3 for thorsten/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"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.3 for phpmyfaq/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"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-6f7dfcd20ebaa48786265499dffa259a","url":"https://github.com/advisories/GHSA-w9xh-5f39-vq89","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-w9xh-5f39-vq89","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.386Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nAn authentication bypass vulnerability in phpMyFAQ allows any unauthenticated attacker to reset the password of any user account, including SuperAdmin accounts. By sending a PUT request with just a valid username and associated email address to /api/user/password/update, an attacker receives a new plaintext password via email without any token verification, rate limiting, or email confirmation. This enables complete account takeover of any user, including full administrative access.\n\n\n### Details\nFile: phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/UnauthorizedUserController.php\nLines: 56-130\nThe updatePassword() method at line 56 accepts PUT requests to /user/password/update with only username and email in the JSON body:\n#[Route(path: 'user/password/update', name: 'api.private.user.password', methods: ['PUT'])]\n```php\npublic function updatePassword(Request $request): JsonResponse\n{\n    $data = json_decode($request->getContent());\n    $username = trim((string) Filter::filterVar($data->username, FILTER_SANITIZE_SPECIAL_CHARS));\n    $email = trim((string) Filter::filterEmail($data->email));\n    if ($username !== '' && $username !== '0' && ($email !== '' && $email !== '0'))","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.3"]},{"certainty":"source_listed","source_ids":["sr-6f7dfcd20ebaa48786265499dffa259a"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nAn authentication bypass vulnerability in phpMyFAQ allows any unauthenticated attacker to reset the password of any user account, including SuperAdmin accounts. By sending a PUT request with just a valid username and associated email address to /api/user/password/update, an attacker receives a new plaintext password via email without any token verification, rate limiting, or email confirmation. This enables complete account takeover of any user, including full administrative access.\n\n\n### Details\nFile: phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/UnauthorizedUserController.php\nLines: 56-130\nThe updatePassword() method at line 56 accepts PUT requests to /user/password/update with only username and email in the JSON body:\n#[Route(path: 'user/password/update', name: 'api.private.user.password', methods: ['PUT'])]\n```php\npublic function updatePassword(Request $request): JsonResponse\n{\n    $data = json_decode($request->getContent());\n    $username = trim((string) Filter::filterVar($data->username, FILTER_SANITIZE_SPECIAL_CHARS));\n    $email = trim((string) Filter::filterEmail($data->email));\n    if ($username !== '' && $username !== '0' && ($email !== '' && $email !== '0'))","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.1.3"]}],"null_published_at":"2026-10-31T22:12:57.138Z","source_updated_at":"2026-09-10T03:50:47.931Z","source_disclosed_at":"2026-05-20T15:46:55.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:41.386Z"}],"next_cursor":null,"snapshot_revision":"42594"}