CVE•Published 2026-07-01•Modified 2026-07-06•0 articles on news•4 live references•NVD data
CVE-2026-53908Mycomplianceoffice · Mycomplianceoffice
Vulnerability data via NVD (ingested)
CVSS v3.1
4.3
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS percentile
24
Exploit Prediction Scoring System · top 76% of all CVEs
Weaknesses (CWE)
Description
MCO is vulnerable to User Enumeration through authentication-related functionalities. The application returns distinguishable responses for valid and invalid users during username reminder and password reset operations. An attacker can leverage these differences to enumerate valid usernames and email addresses. Because vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 25.3.3.1 but may also affect other versions.
Timeline
Published 2026-07-01
Modified 2026-07-06
External references
Search for exposed instances
Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).
Shodan · vuln tag0 hosts
vuln:CVE-2026-53908Hosts Shodan has explicitly fingerprinted as vulnerable.
Shodan · product + version
product:"Mycomplianceoffice Mycomplianceoffice" version:"25.3.3.1"Version-pinned fingerprint from NVD's first vulnerable CPE.
Shodan · banner/body mention
http.html:"Mycomplianceoffice"HTTP body or banner mentions "Mycomplianceoffice" — catches deploys Shodan didn't identify as a product.
More intel sources (5)
Shodan report
vuln:CVE-2026-53908Country / ASN / product breakdown for the vuln query.
Censys
vulnerabilities.cve_id: CVE-2026-53908Censys host search filtered to this CVE id.
grep.app
CVE-2026-53908Public source-code mentions — fast PoC discovery.
GitHub code
CVE-2026-53908GitHub code search for direct mentions.
Google dork
"CVE-2026-53908" exploit -site:nvd.nist.govWrite-ups and news, NVD excluded.
Known PoCs on GitHub (1)
We haven't classified any articles referencing CVE-2026-53908 yet. The external references above still apply.