{"api_version":"v1","generated_at":"2026-10-08T10:35:00+00:00","product":{"cve_count":10,"evidence_gap_note":"Official registry publication history is linked, but a publisher support or retirement boundary has not been established.","id":"security:cve-yifang-cms-36999830aca0","lifecycle_state":"evidence_gap","linked_lifecycle_url":"https://lifecycle.blacktree.nl/libraries/npm/cms","name":"CMS","next_cursor":null,"observations":[{"affected":"2.0.0; 2.0.1; 2.0.2; 2.0.3; 2.0.4; 2.0.5","affected_versions_present":true,"cve_id":"CVE-2026-6633","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-6633","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-04-20T13:01:44.244Z","patch_url":"","primary_source":"","published":"2026-04-20T11:15:11.127Z"},{"affected":"2.0.5","affected_versions_present":true,"cve_id":"CVE-2026-3743","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-3743","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-03-11T19:40:45.437Z","patch_url":"","primary_source":"","published":"2026-03-08T15:02:10.017Z"},{"affected":"2.0.5","affected_versions_present":true,"cve_id":"CVE-2026-3742","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-3742","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-03-11T19:45:55.360Z","patch_url":"","primary_source":"","published":"2026-03-08T15:02:07.812Z"},{"affected":"2.0.5","affected_versions_present":true,"cve_id":"CVE-2026-3741","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-3741","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-03-11T19:46:18.525Z","patch_url":"","primary_source":"","published":"2026-03-08T14:32:10.515Z"},{"affected":"2.0.0; 2.0.1; 2.0.2; 2.0.3; 2.0.4; 2.0.5","affected_versions_present":true,"cve_id":"CVE-2026-2934","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-2934","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-02-25T18:33:35.658Z","patch_url":"","primary_source":"","published":"2026-02-22T08:02:08.708Z"},{"affected":"2.0.0; 2.0.1; 2.0.2; 2.0.3; 2.0.4; 2.0.5","affected_versions_present":true,"cve_id":"CVE-2026-2933","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-2933","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-02-27T18:18:36.765Z","patch_url":"","primary_source":"","published":"2026-02-22T07:32:11.055Z"},{"affected":"2.0.0; 2.0.1; 2.0.2; 2.0.3; 2.0.4; 2.0.5","affected_versions_present":true,"cve_id":"CVE-2026-2932","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-2932","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-02-27T18:15:32.945Z","patch_url":"","primary_source":"","published":"2026-02-22T07:32:08.677Z"},{"affected":"2.0.0; 2.0.1; 2.0.2","affected_versions_present":true,"cve_id":"CVE-2025-11136","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-11136","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-09-29T12:47:12.143Z","patch_url":"","primary_source":"","published":"2025-09-29T02:02:05.045Z"},{"affected":"2.0.0; 2.0.1; 2.0.2; 2.0.3; 2.0.4; 2.0.5","affected_versions_present":true,"cve_id":"CVE-2025-9400","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-9400","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-08-25T20:29:09.150Z","patch_url":"","primary_source":"","published":"2025-08-25T00:32:06.112Z"},{"affected":"2.0.0; 2.0.1; 2.0.2; 2.0.3; 2.0.4; 2.0.5","affected_versions_present":true,"cve_id":"CVE-2025-9399","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-9399","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-08-25T20:28:32.941Z","patch_url":"","primary_source":"","published":"2025-08-25T00:02:05.588Z"},{"affected":"2.0.0; 2.0.1; 2.0.2; 2.0.3; 2.0.4; 2.0.5","affected_versions_present":true,"cve_id":"CVE-2025-9398","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-9398","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-08-25T20:27:57.281Z","patch_url":"","primary_source":"","published":"2025-08-24T23:32:06.686Z"},{"affected":"2.0.0; 2.0.1; 2.0.2","affected_versions_present":true,"cve_id":"CVE-2025-5383","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-5383","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-06-02T15:47:33.395Z","patch_url":"","primary_source":"","published":"2025-05-31T15:00:16.412Z"},{"affected":"2.0.0; 2.0.1; 2.0.2","affected_versions_present":true,"cve_id":"CVE-2025-5381","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-5381","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-06-02T15:47:39.708Z","patch_url":"","primary_source":"","published":"2025-05-31T14:31:10.103Z"}],"source_generated_at":"2026-10-08T06:18:52.353Z","vendor":"Yifang"}}