Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify network-accessible Ech0 instance
-
DeliveryFetch post UUIDs from /api/echo/page
-
ExploitCall /api/comments unauthenticated per post UUID
-
ExecutionParse JSON responses for email fields
-
ImpactHarvest complete guest commenter email list
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The endpoints |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L) accurately reflects low-complexity, unauthenticated network exploitation with limited confidentiality impact confined to the vulnerable system. A published POC Python script in the GHSA advisory trivializes exploitation - only HTTP access to the target is required. No EPSS score was provided in the input data, and no CISA KEV listing is present, so active exploitation cannot be asserted. Real-world urgency derives less from the raw base score and more from privacy-regulatory exposure: bulk harvesting of guest commenter emails enables phishing, spam campaigns, and potential GDPR or equivalent-jurisdiction violations for any operator collecting EU-resident email addresses. The VC:L rating correctly signals that no credentials, keys, or high-value secrets are exposed, distinguishing this from authentication-bypass or RCE class findings - but the zero-friction unauthenticated mass-enumeration aspect elevates practical urgency beyond what the score alone conveys. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a GET request to |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
Ech0 before version 4.7.3 exposes guest commenter email addresses to unauthenticated remote callers via public comment-listing API endpoints, due to a missing json:"-" serialization tag on the Comment model's Email field. Any attacker with HTTP access to an Ech0 instance can enumerate every guest commenter email stored in the database by calling /api/comments or /api/comments/public without credentials. A working proof-of-concept script is published in the GHSA advisory; no public exploit has been confirmed as actively exploited (CISA KEV listing absent).
RemediationAI
Upgrade Ech0 to version 4.7.3 or later, which incorporates the fix from commit cb8d7a997dd8f573ef0e22e4e6b23b2b8ee92ebd; Go module consumers should update to 1.4.8-0.20260503034700-cb8d7a997dd8 or later. Full advisory details are available at https://github.com/lin-snow/Ech0/security/advisories/GHSA-rj4g-rqgh-rx9h. As a compensating control before patching, operators may configure a reverse proxy or WAF rule to block unauthenticated external access to the /api/comments and /api/comments/public paths; note this may break public comment display if the frontend fetches these endpoints client-side, so functional testing against the UI is necessary before deploying this restriction. No other vendor-documented workaround exists.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in go, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Ech0 is a self-hosted Go blogging and microblogging platform using the Gin web framework and GORM ORM. The vulnerability resides in the Comment struct at internal/model/comment/comment.go:33, where the Email field carries the tag json:"email" rather than json:"-". Adjacent PII fields IPHash and UserAgent already use json:"-", demonstrating developer intent to suppress server-side PII from API responses - the Email field was inadvertently omitted from this protection. GORM hydrates the full Comment struct from the database, and the Gin handlers for both GET /api/comments and GET /api/comments/public call ctx.JSON on the raw struct slice with no DTO projection or field filtering. Both routes are registered under PublicRouterGroup (router file internal/router/comment.go:20) with no authentication middleware. The root cause class is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor). A prior related disclosure (GHSA-m983-7426-5hrj, March 2026) patched a similar leak on /api/allusers exposing registered account-owner emails; this CVE covers distinct endpoints and a distinct data subject (guest commenters, not registered accounts).
Know when Ech0 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Unauthenticated network access exposes only email strings from a single system with no integrity or availability impact, yielding C:L, I:N, A:N, S:U.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
1DescriptionCVE.org
Ech0 versions before 4.7.3 expose guest commenter email addresses through public API endpoints due to improper JSON serialization tags on the Comment model. Unauthenticated attackers can harvest all commenter emails by calling the /api/comments and /api/comments/public endpoints without authentication.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Persistent authentication bypass in Ech0 (lin-snow's self-hosted lightweight publishing/memo app) before 4.7.3 lets an a
OAuth redirect URI validation in Ech0 through 4.5.6 allows session hijacking via exchange-code theft by exploiting incom
Authorization bypass in Ech0 before 4.5.1 allows any authenticated non-admin user to invoke privileged admin endpoints b
Denial of service in Ech0 before 5.0.1 allows unauthenticated remote attackers to saturate server CPU by exploiting a qu
Privilege escalation in Ech0 before 4.4.3 allows an attacker holding an admin's profile:read access token to change the
Server-side request forgery in Ech0 before version 4.7.3 allows authenticated users to pivot through the application ser
Scope enforcement in Ech0 4.3.4 and earlier is opt-in at the route level, meaning privileged admin routes that omit the
Missing administrator authorization on dashboard log endpoints in Ech0 before 4.4.3 allows any authenticated low-privile
Scope enforcement bypass in Ech0's comment panel admin API allows any holder of a valid admin-issued access token - rega
Unauthenticated metric inflation in Ech0 before 4.7.3 allows any remote attacker to arbitrarily increment the fav_count
Unauthenticated remote attackers can increment the fav_count of any echo - including private ones - in Ech0 through 4.5.
Unsalted MD5 password hashing in Ech0's `MD5Encrypt` function (`internal/util/crypto/crypto.go`) stores credentials in a
EUVD-2026-65454
GHSA-845p-52xj-2432
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB