{"items":[{"id":"NVI-00004104","kind":"vulnerability","title":"phpMyFAQ duplicate email registration allows multiple accounts with the same email","revision":5,"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-9wj2-4hcm-r74j","CVE-2025-59943"],"plain_summary":"OSV carries this publisher advisory for thorsten/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.0.13 for thorsten/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-5808e327e6ef2cd086a5e97b42d295c7"],"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-2db14721adae6920770e787a7d5b2758"],"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-08T22:10:00.563Z","value":"8.1 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-c5bf652d19081513cba0ba66822f0297"},{"kind":"CVSS","as_of":"2026-10-08T22:10:00.563Z","value":"9.8 CRITICAL (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-c5bf652d19081513cba0ba66822f0297"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.416%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.35911. Missing scores are unknown.","source_id":"sr-2db14721adae6920770e787a7d5b2758"}],"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-5808e327e6ef2cd086a5e97b42d295c7","url":"https://github.com/advisories/GHSA-9wj2-4hcm-r74j","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9wj2-4hcm-r74j","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.691Z"},{"id":"sr-c5bf652d19081513cba0ba66822f0297","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-59943","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2025-59943","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:22.167Z"},{"id":"sr-2db14721adae6920770e787a7d5b2758","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-2025-59943","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.835Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5808e327e6ef2cd086a5e97b42d295c7"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nphpMyFAQ does not enforce uniqueness of email addresses during user registration. This allows multiple distinct accounts to be created with the same email. Because email is often used as an identifier for password resets, notifications, and administrative actions, this flaw can cause account ambiguity and, in certain configurations, may lead to privilege escalation or account takeover.\n\n### Details\nAn account management logic flaw in phpMyFAQ allows attackers to register multiple accounts under the same email address. If email is used for password reset or administrative flows, this may result in account takeover, loss of accountability, and abuse of business logic.\n### PoC\n\n1.Register  a user with email test@example.com\n2.Register another user with the same email.\n3.Both accounts appear in /admin/?action=user&user_action=listallusers.\n\n\n### Impact\n\n-Data integrity loss: Multiple accounts mapped to one email break auditability.\n-Password reset ambiguity: If reset flow relies on email only, attackers can target or take over accounts.\n-Privile","public_affected_ranges":["ECOSYSTEM: introduced 4.0.7; fixed 4.0.13"]}],"null_published_at":"2026-11-08T19:53:38.920Z","source_updated_at":"2026-09-10T03:50:29.527Z","source_disclosed_at":"2025-10-03T14:52:33.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:10.691Z"},{"id":"NVI-00004104","kind":"vulnerability","title":"phpMyFAQ duplicate email registration allows multiple accounts with the same email","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-9wj2-4hcm-r74j","CVE-2025-59943"],"plain_summary":"OSV carries this publisher advisory for thorsten/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.0.13 for thorsten/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-5808e327e6ef2cd086a5e97b42d295c7"],"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-1d0dce4fdb419e6a9c3022640dec5143"],"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-08T22:10:00.563Z","value":"8.1 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-c5bf652d19081513cba0ba66822f0297"},{"kind":"CVSS","as_of":"2026-10-08T22:10:00.563Z","value":"9.8 CRITICAL (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-c5bf652d19081513cba0ba66822f0297"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.416%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.3592. Missing scores are unknown.","source_id":"sr-1d0dce4fdb419e6a9c3022640dec5143"}],"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-5808e327e6ef2cd086a5e97b42d295c7","url":"https://github.com/advisories/GHSA-9wj2-4hcm-r74j","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9wj2-4hcm-r74j","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.691Z"},{"id":"sr-c5bf652d19081513cba0ba66822f0297","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-59943","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2025-59943","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:22.167Z"},{"id":"sr-1d0dce4fdb419e6a9c3022640dec5143","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-2025-59943","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.260Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5808e327e6ef2cd086a5e97b42d295c7"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nphpMyFAQ does not enforce uniqueness of email addresses during user registration. This allows multiple distinct accounts to be created with the same email. Because email is often used as an identifier for password resets, notifications, and administrative actions, this flaw can cause account ambiguity and, in certain configurations, may lead to privilege escalation or account takeover.\n\n### Details\nAn account management logic flaw in phpMyFAQ allows attackers to register multiple accounts under the same email address. If email is used for password reset or administrative flows, this may result in account takeover, loss of accountability, and abuse of business logic.\n### PoC\n\n1.Register  a user with email test@example.com\n2.Register another user with the same email.\n3.Both accounts appear in /admin/?action=user&user_action=listallusers.\n\n\n### Impact\n\n-Data integrity loss: Multiple accounts mapped to one email break auditability.\n-Password reset ambiguity: If reset flow relies on email only, attackers can target or take over accounts.\n-Privile","public_affected_ranges":["ECOSYSTEM: introduced 4.0.7; fixed 4.0.13"]}],"null_published_at":"2026-11-07T22:29:23.419Z","source_updated_at":"2026-09-10T03:50:29.527Z","source_disclosed_at":"2025-10-03T14:52:33.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:10.691Z"},{"id":"NVI-00004104","kind":"vulnerability","title":"phpMyFAQ duplicate email registration allows multiple accounts with the same email","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-9wj2-4hcm-r74j","CVE-2025-59943"],"plain_summary":"OSV carries this publisher advisory for thorsten/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.0.13 for thorsten/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-5808e327e6ef2cd086a5e97b42d295c7"],"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-1d0dce4fdb419e6a9c3022640dec5143"],"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-01T12:00:16.000Z","value":"0.416%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.3592. Missing scores are unknown.","source_id":"sr-1d0dce4fdb419e6a9c3022640dec5143"}],"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-5808e327e6ef2cd086a5e97b42d295c7","url":"https://github.com/advisories/GHSA-9wj2-4hcm-r74j","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9wj2-4hcm-r74j","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.691Z"},{"id":"sr-1d0dce4fdb419e6a9c3022640dec5143","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-2025-59943","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.260Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5808e327e6ef2cd086a5e97b42d295c7"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nphpMyFAQ does not enforce uniqueness of email addresses during user registration. This allows multiple distinct accounts to be created with the same email. Because email is often used as an identifier for password resets, notifications, and administrative actions, this flaw can cause account ambiguity and, in certain configurations, may lead to privilege escalation or account takeover.\n\n### Details\nAn account management logic flaw in phpMyFAQ allows attackers to register multiple accounts under the same email address. If email is used for password reset or administrative flows, this may result in account takeover, loss of accountability, and abuse of business logic.\n### PoC\n\n1.Register  a user with email test@example.com\n2.Register another user with the same email.\n3.Both accounts appear in /admin/?action=user&user_action=listallusers.\n\n\n### Impact\n\n-Data integrity loss: Multiple accounts mapped to one email break auditability.\n-Password reset ambiguity: If reset flow relies on email only, attackers can target or take over accounts.\n-Privile","public_affected_ranges":["ECOSYSTEM: introduced 4.0.7; fixed 4.0.13"]}],"null_published_at":"2026-11-04T18:04:03.124Z","source_updated_at":"2026-09-10T03:50:29.527Z","source_disclosed_at":"2025-10-03T14:52:33.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:10.691Z"},{"id":"NVI-00004104","kind":"vulnerability","title":"phpMyFAQ duplicate email registration allows multiple accounts with the same email","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-9wj2-4hcm-r74j","CVE-2025-59943"],"plain_summary":"OSV carries this publisher advisory for thorsten/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.0.13 for thorsten/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-5808e327e6ef2cd086a5e97b42d295c7"],"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-5294f3427a75b5528cf3791ddd3e4a2f"],"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.416%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.35928. Missing scores are unknown.","source_id":"sr-5294f3427a75b5528cf3791ddd3e4a2f"}],"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-5808e327e6ef2cd086a5e97b42d295c7","url":"https://github.com/advisories/GHSA-9wj2-4hcm-r74j","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9wj2-4hcm-r74j","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.691Z"},{"id":"sr-5294f3427a75b5528cf3791ddd3e4a2f","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-2025-59943","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.372Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5808e327e6ef2cd086a5e97b42d295c7"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nphpMyFAQ does not enforce uniqueness of email addresses during user registration. This allows multiple distinct accounts to be created with the same email. Because email is often used as an identifier for password resets, notifications, and administrative actions, this flaw can cause account ambiguity and, in certain configurations, may lead to privilege escalation or account takeover.\n\n### Details\nAn account management logic flaw in phpMyFAQ allows attackers to register multiple accounts under the same email address. If email is used for password reset or administrative flows, this may result in account takeover, loss of accountability, and abuse of business logic.\n### PoC\n\n1.Register  a user with email test@example.com\n2.Register another user with the same email.\n3.Both accounts appear in /admin/?action=user&user_action=listallusers.\n\n\n### Impact\n\n-Data integrity loss: Multiple accounts mapped to one email break auditability.\n-Password reset ambiguity: If reset flow relies on email only, attackers can target or take over accounts.\n-Privile","public_affected_ranges":["ECOSYSTEM: introduced 4.0.7; fixed 4.0.13"]}],"null_published_at":"2026-11-01T01:04:04.830Z","source_updated_at":"2026-09-10T03:50:29.527Z","source_disclosed_at":"2025-10-03T14:52:33.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:10.691Z"},{"id":"NVI-00004104","kind":"vulnerability","title":"phpMyFAQ duplicate email registration allows multiple accounts with the same email","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-9wj2-4hcm-r74j","CVE-2025-59943"],"plain_summary":"OSV carries this publisher advisory for thorsten/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.0.13 for thorsten/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-5808e327e6ef2cd086a5e97b42d295c7"],"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-5808e327e6ef2cd086a5e97b42d295c7","url":"https://github.com/advisories/GHSA-9wj2-4hcm-r74j","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-9wj2-4hcm-r74j","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.691Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5808e327e6ef2cd086a5e97b42d295c7"],"technology":"thorsten/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nphpMyFAQ does not enforce uniqueness of email addresses during user registration. This allows multiple distinct accounts to be created with the same email. Because email is often used as an identifier for password resets, notifications, and administrative actions, this flaw can cause account ambiguity and, in certain configurations, may lead to privilege escalation or account takeover.\n\n### Details\nAn account management logic flaw in phpMyFAQ allows attackers to register multiple accounts under the same email address. If email is used for password reset or administrative flows, this may result in account takeover, loss of accountability, and abuse of business logic.\n### PoC\n\n1.Register  a user with email test@example.com\n2.Register another user with the same email.\n3.Both accounts appear in /admin/?action=user&user_action=listallusers.\n\n\n### Impact\n\n-Data integrity loss: Multiple accounts mapped to one email break auditability.\n-Password reset ambiguity: If reset flow relies on email only, attackers can target or take over accounts.\n-Privile","public_affected_ranges":["ECOSYSTEM: introduced 4.0.7; fixed 4.0.13"]}],"null_published_at":"2026-10-31T22:12:52.628Z","source_updated_at":"2026-09-10T03:50:29.527Z","source_disclosed_at":"2025-10-03T14:52:33.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:10.691Z"}],"next_cursor":null,"snapshot_revision":"42594"}