{"items":[{"id":"NVI-00004068","kind":"vulnerability","title":"Froxlor username/surname AND company field Bypass","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-625g-fm5w-w7w4","CVE-2023-50256"],"plain_summary":"OSV carries this publisher advisory for froxlor/froxlor. 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 2.1.2 for froxlor/froxlor. Confirm the publisher’s latest guidance.","source_ids":["sr-56ac96c5af32936ded1ff00801dd47d2"],"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-0a6be3b83e5f44af5f553cd0d1440158"],"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-17T06:39:23.720Z","value":"7.5 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-2d38fd4e33165ffe7c52591402b64a74"},{"kind":"CVSS","as_of":"2026-06-17T06:39:23.720Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-2d38fd4e33165ffe7c52591402b64a74"},{"kind":"EPSS","as_of":"2026-11-05T12:03:04.000Z","value":"0.716%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.53934. Missing scores are unknown.","source_id":"sr-0a6be3b83e5f44af5f553cd0d1440158"}],"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-56ac96c5af32936ded1ff00801dd47d2","url":"https://github.com/advisories/GHSA-625g-fm5w-w7w4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-625g-fm5w-w7w4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.928Z"},{"id":"sr-2d38fd4e33165ffe7c52591402b64a74","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-50256","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2023-50256","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:58:59.624Z"},{"id":"sr-0a6be3b83e5f44af5f553cd0d1440158","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-2023-50256","publisher":"FIRST EPSS","observed_at":"2026-11-06T00:23:23.954Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-56ac96c5af32936ded1ff00801dd47d2"],"technology":"froxlor/froxlor","known_exclusions":[],"conditions_summary":"Dear Sirs and Madams,\n\nI would like to report a business logic error vulnerability that I discovered during my recent penetration test on Froxlor.\n\nSpecifically, I identified an issue where it was possible to submit the registration form with the essential fields, such as the username and password, left intentionally blank. This inadvertent omission allowed for a bypass of the mandatory field requirements established by the system.\n\nThe surname, family name AND company name all of them can be left blank.\n\nI believe addressing this vulnerability is crucial to ensure the security and integrity of the Froxlor platform.\n\nThank you for your attention to this matter.\n\nThis action served as a means to bypass the mandatory field requirements.\n\nLets see (please have a look at the Video -> attachment).\n\n----------------\n\nas you can see i was able to let the username and second name blank. \n\nhttps://user-images.githubusercontent.com/80028768/289675319-81ae8ebe-1308-4ee3-bedb-43cdc40da474.mp4\n\n\nLets see again.\n\nOnly the company name is set. \n\nThank you for your time\n\n!Froxlor 2\n![Froxlor 1]","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 2.1.2"]}],"null_published_at":"2026-11-08T15:11:49.418Z","source_updated_at":"2026-09-10T03:50:04.871Z","source_disclosed_at":"2024-01-04T17:20:03.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:41:59.928Z"},{"id":"NVI-00004068","kind":"vulnerability","title":"Froxlor username/surname AND company field Bypass","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-625g-fm5w-w7w4","CVE-2023-50256"],"plain_summary":"OSV carries this publisher advisory for froxlor/froxlor. 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 2.1.2 for froxlor/froxlor. Confirm the publisher’s latest guidance.","source_ids":["sr-56ac96c5af32936ded1ff00801dd47d2"],"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-520f4cc1e962fa971dea8754aaaf425f"],"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-17T06:39:23.720Z","value":"7.5 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-2d38fd4e33165ffe7c52591402b64a74"},{"kind":"CVSS","as_of":"2026-06-17T06:39:23.720Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-2d38fd4e33165ffe7c52591402b64a74"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.716%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.53807. Missing scores are unknown.","source_id":"sr-520f4cc1e962fa971dea8754aaaf425f"}],"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-56ac96c5af32936ded1ff00801dd47d2","url":"https://github.com/advisories/GHSA-625g-fm5w-w7w4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-625g-fm5w-w7w4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.928Z"},{"id":"sr-2d38fd4e33165ffe7c52591402b64a74","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-50256","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2023-50256","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:58:59.624Z"},{"id":"sr-520f4cc1e962fa971dea8754aaaf425f","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-2023-50256","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-56ac96c5af32936ded1ff00801dd47d2"],"technology":"froxlor/froxlor","known_exclusions":[],"conditions_summary":"Dear Sirs and Madams,\n\nI would like to report a business logic error vulnerability that I discovered during my recent penetration test on Froxlor.\n\nSpecifically, I identified an issue where it was possible to submit the registration form with the essential fields, such as the username and password, left intentionally blank. This inadvertent omission allowed for a bypass of the mandatory field requirements established by the system.\n\nThe surname, family name AND company name all of them can be left blank.\n\nI believe addressing this vulnerability is crucial to ensure the security and integrity of the Froxlor platform.\n\nThank you for your attention to this matter.\n\nThis action served as a means to bypass the mandatory field requirements.\n\nLets see (please have a look at the Video -> attachment).\n\n----------------\n\nas you can see i was able to let the username and second name blank. \n\nhttps://user-images.githubusercontent.com/80028768/289675319-81ae8ebe-1308-4ee3-bedb-43cdc40da474.mp4\n\n\nLets see again.\n\nOnly the company name is set. \n\nThank you for your time\n\n!Froxlor 2\n![Froxlor 1]","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 2.1.2"]}],"null_published_at":"2026-11-01T01:04:04.829Z","source_updated_at":"2026-09-10T03:50:04.871Z","source_disclosed_at":"2024-01-04T17:20:03.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:41:59.928Z"},{"id":"NVI-00004068","kind":"vulnerability","title":"Froxlor username/surname AND company field Bypass","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-625g-fm5w-w7w4","CVE-2023-50256"],"plain_summary":"OSV carries this publisher advisory for froxlor/froxlor. 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 2.1.2 for froxlor/froxlor. Confirm the publisher’s latest guidance.","source_ids":["sr-56ac96c5af32936ded1ff00801dd47d2"],"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-56ac96c5af32936ded1ff00801dd47d2","url":"https://github.com/advisories/GHSA-625g-fm5w-w7w4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-625g-fm5w-w7w4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.928Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-56ac96c5af32936ded1ff00801dd47d2"],"technology":"froxlor/froxlor","known_exclusions":[],"conditions_summary":"Dear Sirs and Madams,\n\nI would like to report a business logic error vulnerability that I discovered during my recent penetration test on Froxlor.\n\nSpecifically, I identified an issue where it was possible to submit the registration form with the essential fields, such as the username and password, left intentionally blank. This inadvertent omission allowed for a bypass of the mandatory field requirements established by the system.\n\nThe surname, family name AND company name all of them can be left blank.\n\nI believe addressing this vulnerability is crucial to ensure the security and integrity of the Froxlor platform.\n\nThank you for your attention to this matter.\n\nThis action served as a means to bypass the mandatory field requirements.\n\nLets see (please have a look at the Video -> attachment).\n\n----------------\n\nas you can see i was able to let the username and second name blank. \n\nhttps://user-images.githubusercontent.com/80028768/289675319-81ae8ebe-1308-4ee3-bedb-43cdc40da474.mp4\n\n\nLets see again.\n\nOnly the company name is set. \n\nThank you for your time\n\n!Froxlor 2\n![Froxlor 1]","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 2.1.2"]}],"null_published_at":"2026-10-31T22:12:52.616Z","source_updated_at":"2026-09-10T03:50:04.871Z","source_disclosed_at":"2024-01-04T17:20:03.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:41:59.928Z"}],"next_cursor":null,"snapshot_revision":"42594"}