{"items":[{"id":"NVI-00005860","kind":"vulnerability","title":"phpMyFAQ SQL Injection at \"Save News\"","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-qgxx-4xv5-6hcw","CVE-2024-27299"],"plain_summary":"OSV carries this publisher advisory for 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 3.2.6 for phpmyfaq/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-9f40e0372c6c463af24220b2a57bcb40"],"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-0e30c81abf9e02ad26fcbb721e2809ad"],"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-06-17T07:19:36.077Z","value":"8.8 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-42cd187a8c1b18cd3993210da9d2da99"},{"kind":"CVSS","as_of":"2026-06-17T07:19:36.077Z","value":"8.8 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-42cd187a8c1b18cd3993210da9d2da99"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"1.151%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.6691. Missing scores are unknown.","source_id":"sr-0e30c81abf9e02ad26fcbb721e2809ad"}],"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-9f40e0372c6c463af24220b2a57bcb40","url":"https://github.com/advisories/GHSA-qgxx-4xv5-6hcw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-qgxx-4xv5-6hcw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:31.003Z"},{"id":"sr-42cd187a8c1b18cd3993210da9d2da99","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27299","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-27299","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:14.650Z"},{"id":"sr-0e30c81abf9e02ad26fcbb721e2809ad","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-2024-27299","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:14:50.774Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-9f40e0372c6c463af24220b2a57bcb40"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nA SQL injection vulnerability has been discovered in the the \"Add News\" functionality due to improper escaping of the email address. This allows any authenticated user with the rights to add/edit FAQ news to exploit this vulnerability to exfiltrate data, take over accounts and in some cases, even achieve RCE.\n\n### Details\nThe vulnerable field lies in the  `authorEmail` field which uses PHP's `FILTER_VALIDATE_EMAIL` filter. This filter is insufficient in protecting against SQL injection attacks and should still be properly escaped. However, in this version of phpMyFAQ (3.2.5), this field is not escaped properly can be used together with other fields to fully exploit the SQL injection vulnerability.\n\n### PoCs\n4 PoCs are demonstrated here to illustrate the potential impacts.\n\n#### PoC 1 - Postgres Time Based SQLi\n1. Login as admin or any user with the rights to view and save news.\n2. Navigate to \"../phpmyfaq/admin/?action=news\", click on \"Add news\", fill in some data, send and intercept the request.\n3. Modify the intercepted \"/admin/?action=save-news\" request to look like the SS below:\n    3.1 - Set the \"authorEmail\" field in the body to \"`test'/*@[email.com](http://email.","public_affected_ranges":["ECOSYSTEM: introduced 3.2.5; fixed 3.2.6"]}],"null_published_at":"2026-11-04T10:04:47.595Z","source_updated_at":"2026-09-10T03:50:10.809Z","source_disclosed_at":"2024-03-25T19:44:05.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:31.003Z"},{"id":"NVI-00005860","kind":"vulnerability","title":"phpMyFAQ SQL Injection at \"Save News\"","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-qgxx-4xv5-6hcw","CVE-2024-27299"],"plain_summary":"OSV carries this publisher advisory for 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 3.2.6 for phpmyfaq/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-9f40e0372c6c463af24220b2a57bcb40"],"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-6903941cc2ca322bd7c93e105773110c"],"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-06-17T07:19:36.077Z","value":"8.8 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-42cd187a8c1b18cd3993210da9d2da99"},{"kind":"CVSS","as_of":"2026-06-17T07:19:36.077Z","value":"8.8 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-42cd187a8c1b18cd3993210da9d2da99"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"1.151%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.66913. Missing scores are unknown.","source_id":"sr-6903941cc2ca322bd7c93e105773110c"}],"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-9f40e0372c6c463af24220b2a57bcb40","url":"https://github.com/advisories/GHSA-qgxx-4xv5-6hcw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-qgxx-4xv5-6hcw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:31.003Z"},{"id":"sr-42cd187a8c1b18cd3993210da9d2da99","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27299","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-27299","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:14.650Z"},{"id":"sr-6903941cc2ca322bd7c93e105773110c","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-2024-27299","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-9f40e0372c6c463af24220b2a57bcb40"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nA SQL injection vulnerability has been discovered in the the \"Add News\" functionality due to improper escaping of the email address. This allows any authenticated user with the rights to add/edit FAQ news to exploit this vulnerability to exfiltrate data, take over accounts and in some cases, even achieve RCE.\n\n### Details\nThe vulnerable field lies in the  `authorEmail` field which uses PHP's `FILTER_VALIDATE_EMAIL` filter. This filter is insufficient in protecting against SQL injection attacks and should still be properly escaped. However, in this version of phpMyFAQ (3.2.5), this field is not escaped properly can be used together with other fields to fully exploit the SQL injection vulnerability.\n\n### PoCs\n4 PoCs are demonstrated here to illustrate the potential impacts.\n\n#### PoC 1 - Postgres Time Based SQLi\n1. Login as admin or any user with the rights to view and save news.\n2. Navigate to \"../phpmyfaq/admin/?action=news\", click on \"Add news\", fill in some data, send and intercept the request.\n3. Modify the intercepted \"/admin/?action=save-news\" request to look like the SS below:\n    3.1 - Set the \"authorEmail\" field in the body to \"`test'/*@[email.com](http://email.","public_affected_ranges":["ECOSYSTEM: introduced 3.2.5; fixed 3.2.6"]}],"null_published_at":"2026-11-01T01:45:40.745Z","source_updated_at":"2026-09-10T03:50:10.809Z","source_disclosed_at":"2024-03-25T19:44:05.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:31.003Z"},{"id":"NVI-00005860","kind":"vulnerability","title":"phpMyFAQ SQL Injection at \"Save News\"","revision":2,"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-qgxx-4xv5-6hcw","CVE-2024-27299"],"plain_summary":"OSV carries this publisher advisory for 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 3.2.6 for phpmyfaq/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-9f40e0372c6c463af24220b2a57bcb40"],"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-42cd187a8c1b18cd3993210da9d2da99"],"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-06-17T07:19:36.077Z","value":"8.8 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-42cd187a8c1b18cd3993210da9d2da99"},{"kind":"CVSS","as_of":"2026-06-17T07:19:36.077Z","value":"8.8 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-42cd187a8c1b18cd3993210da9d2da99"}],"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-9f40e0372c6c463af24220b2a57bcb40","url":"https://github.com/advisories/GHSA-qgxx-4xv5-6hcw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-qgxx-4xv5-6hcw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:31.003Z"},{"id":"sr-42cd187a8c1b18cd3993210da9d2da99","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27299","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-27299","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:14.650Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-9f40e0372c6c463af24220b2a57bcb40"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nA SQL injection vulnerability has been discovered in the the \"Add News\" functionality due to improper escaping of the email address. This allows any authenticated user with the rights to add/edit FAQ news to exploit this vulnerability to exfiltrate data, take over accounts and in some cases, even achieve RCE.\n\n### Details\nThe vulnerable field lies in the  `authorEmail` field which uses PHP's `FILTER_VALIDATE_EMAIL` filter. This filter is insufficient in protecting against SQL injection attacks and should still be properly escaped. However, in this version of phpMyFAQ (3.2.5), this field is not escaped properly can be used together with other fields to fully exploit the SQL injection vulnerability.\n\n### PoCs\n4 PoCs are demonstrated here to illustrate the potential impacts.\n\n#### PoC 1 - Postgres Time Based SQLi\n1. Login as admin or any user with the rights to view and save news.\n2. Navigate to \"../phpmyfaq/admin/?action=news\", click on \"Add news\", fill in some data, send and intercept the request.\n3. Modify the intercepted \"/admin/?action=save-news\" request to look like the SS below:\n    3.1 - Set the \"authorEmail\" field in the body to \"`test'/*@[email.com](http://email.","public_affected_ranges":["ECOSYSTEM: introduced 3.2.5; fixed 3.2.6"]}],"null_published_at":"2026-11-01T01:04:04.826Z","source_updated_at":"2026-09-10T03:50:10.809Z","source_disclosed_at":"2024-03-25T19:44:05.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:31.003Z"},{"id":"NVI-00005860","kind":"vulnerability","title":"phpMyFAQ SQL Injection at \"Save News\"","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-qgxx-4xv5-6hcw","CVE-2024-27299"],"plain_summary":"OSV carries this publisher advisory for 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 3.2.6 for phpmyfaq/phpmyfaq. Confirm the publisher’s latest guidance.","source_ids":["sr-9f40e0372c6c463af24220b2a57bcb40"],"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-9f40e0372c6c463af24220b2a57bcb40","url":"https://github.com/advisories/GHSA-qgxx-4xv5-6hcw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-qgxx-4xv5-6hcw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:31.003Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-9f40e0372c6c463af24220b2a57bcb40"],"technology":"phpmyfaq/phpmyfaq","known_exclusions":[],"conditions_summary":"### Summary\nA SQL injection vulnerability has been discovered in the the \"Add News\" functionality due to improper escaping of the email address. This allows any authenticated user with the rights to add/edit FAQ news to exploit this vulnerability to exfiltrate data, take over accounts and in some cases, even achieve RCE.\n\n### Details\nThe vulnerable field lies in the  `authorEmail` field which uses PHP's `FILTER_VALIDATE_EMAIL` filter. This filter is insufficient in protecting against SQL injection attacks and should still be properly escaped. However, in this version of phpMyFAQ (3.2.5), this field is not escaped properly can be used together with other fields to fully exploit the SQL injection vulnerability.\n\n### PoCs\n4 PoCs are demonstrated here to illustrate the potential impacts.\n\n#### PoC 1 - Postgres Time Based SQLi\n1. Login as admin or any user with the rights to view and save news.\n2. Navigate to \"../phpmyfaq/admin/?action=news\", click on \"Add news\", fill in some data, send and intercept the request.\n3. Modify the intercepted \"/admin/?action=save-news\" request to look like the SS below:\n    3.1 - Set the \"authorEmail\" field in the body to \"`test'/*@[email.com](http://email.","public_affected_ranges":["ECOSYSTEM: introduced 3.2.5; fixed 3.2.6"]}],"null_published_at":"2026-10-31T22:13:05.841Z","source_updated_at":"2026-09-10T03:50:10.809Z","source_disclosed_at":"2024-03-25T19:44:05.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:31.003Z"}],"next_cursor":null,"snapshot_revision":"42594"}