{"items":[{"id":"NVI-00003844","kind":"vulnerability","title":"YesWiki Uses a Broken or Risky Cryptographic Algorithm","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-4fvx-h823-38v3","CVE-2024-51478"],"plain_summary":"OSV carries this publisher advisory for yeswiki/yeswiki. 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.4.5 for yeswiki/yeswiki. Confirm the publisher’s latest guidance.","source_ids":["sr-4cfd1f0cf6eb09c185c13ebb21ab6211"],"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-a51b3a00b7086a4b5009ef177c37bc68"],"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.373%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.31316. Missing scores are unknown.","source_id":"sr-a51b3a00b7086a4b5009ef177c37bc68"}],"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-4cfd1f0cf6eb09c185c13ebb21ab6211","url":"https://github.com/advisories/GHSA-4fvx-h823-38v3","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-4fvx-h823-38v3","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.668Z"},{"id":"sr-a51b3a00b7086a4b5009ef177c37bc68","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-51478","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.369Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4cfd1f0cf6eb09c185c13ebb21ab6211"],"technology":"yeswiki/yeswiki","known_exclusions":[],"conditions_summary":"### Summary\nThe use of a weak cryptographic algorithm and a hard-coded salt to hash the password reset key allows it to be recovered and used to reset the password of any account.\n\n### Details\nFirstly, the salt used to hash the password reset key is hard-coded in the `includes/services/UserManager.php` file at line `36` :\n\n```php\nprivate const PW_SALT = 'FBcA';\n```\n\nNext, the application uses a weak cryptographic algorithm to hash the password reset key. The hash algorithm is defined in the `includes/services/UserManager.php` file at line `201` :\n\n```php\nprotected function generateUserLink($user)\n{\n    // Generate the password recovery key\n    $key = md5($user['name'] . '_' . $user['email'] . random_int(0, 10000) . date('Y-m-d H:i:s') . self::PW_SALT);\n```\n\nThe key is generated from the **user's name**, **e-mail address**, a random number **between 0 and 10000**, the **current date** of the request and the **salt**.\nIf we know the user's name and e-mail address, we can retrieve the key and use it to reset the account password with a bit of brute force on the random number.\n\n### Proof of Concept (PoC)\nTo demonstrate the vulnerability, I created a python script to automatically retri","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.4.5"]}],"null_published_at":"2026-11-04T02:53:03.187Z","source_updated_at":"2024-10-31T19:49:34.458Z","source_disclosed_at":"2024-10-31T17:12:35.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:49.668Z"},{"id":"NVI-00003844","kind":"vulnerability","title":"YesWiki Uses a Broken or Risky Cryptographic Algorithm","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-4fvx-h823-38v3","CVE-2024-51478"],"plain_summary":"OSV carries this publisher advisory for yeswiki/yeswiki. 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.4.5 for yeswiki/yeswiki. Confirm the publisher’s latest guidance.","source_ids":["sr-4cfd1f0cf6eb09c185c13ebb21ab6211"],"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-4cfd1f0cf6eb09c185c13ebb21ab6211","url":"https://github.com/advisories/GHSA-4fvx-h823-38v3","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-4fvx-h823-38v3","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.668Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4cfd1f0cf6eb09c185c13ebb21ab6211"],"technology":"yeswiki/yeswiki","known_exclusions":[],"conditions_summary":"### Summary\nThe use of a weak cryptographic algorithm and a hard-coded salt to hash the password reset key allows it to be recovered and used to reset the password of any account.\n\n### Details\nFirstly, the salt used to hash the password reset key is hard-coded in the `includes/services/UserManager.php` file at line `36` :\n\n```php\nprivate const PW_SALT = 'FBcA';\n```\n\nNext, the application uses a weak cryptographic algorithm to hash the password reset key. The hash algorithm is defined in the `includes/services/UserManager.php` file at line `201` :\n\n```php\nprotected function generateUserLink($user)\n{\n    // Generate the password recovery key\n    $key = md5($user['name'] . '_' . $user['email'] . random_int(0, 10000) . date('Y-m-d H:i:s') . self::PW_SALT);\n```\n\nThe key is generated from the **user's name**, **e-mail address**, a random number **between 0 and 10000**, the **current date** of the request and the **salt**.\nIf we know the user's name and e-mail address, we can retrieve the key and use it to reset the account password with a bit of brute force on the random number.\n\n### Proof of Concept (PoC)\nTo demonstrate the vulnerability, I created a python script to automatically retri","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 4.4.5"]}],"null_published_at":"2026-10-31T22:12:52.599Z","source_updated_at":"2024-10-31T19:49:34.458Z","source_disclosed_at":"2024-10-31T17:12:35.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:49.668Z"}],"next_cursor":null,"snapshot_revision":"42594"}