{"vulnerability": "cve-2025-21626", "sightings": [{"uuid": "2e77863e-9ebe-4da3-9ff7-18a78d6f0cd5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21626", "type": "seen", "source": "MISP/8e1b6542-ae86-4729-a7a6-4e9f670b8bb7", "content": "", "creation_timestamp": "2025-08-22T17:25:06.000000Z"}, {"uuid": "dfb1b71b-6309-489d-938d-8c35ca9e79bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21626", "type": "seen", "source": "https://t.me/cvedetector/18899", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21626 - GLPI Information Disclosure Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21626 \nPublished : Feb. 25, 2025, 4:15 p.m. | 1\u00a0hour, 37\u00a0minutes ago \nDescription : GLPI is a free asset and IT management software package. Starting in version 0.71 and prior to version 10.0.18, an anonymous user can fetch sensitive information from the `status.php` endpoint. Version 10.0.18 contains a fix for the issue. Some workarounds are available. One may delete the `status.php` file, restrict its access, or remove any sensitive values from the `name` field of the active LDAP directories, mail servers authentication providers and mail receivers. \nSeverity: 5.8 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-25T19:03:38.000000Z"}]}