<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[🚨 🇻🇪 Sensitive Data Exposure at the Venezuelan Football Federation (FVF)]]></title><description><![CDATA[<p><img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f6a8.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--rotating_light" style="height:23px;width:auto;vertical-align:middle" title="🚨" alt="🚨" /> <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f1fb-1f1ea.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--flag-ve" style="height:23px;width:auto;vertical-align:middle" title="🇻🇪" alt="🇻🇪" /> Sensitive Data Exposure at the Venezuelan Football Federation (FVF)</p><p>The Venezuelan Football Federation (FVF) maintained a publicly accessible storage system that exposed sensitive information belonging to several football clubs, including:</p><p>Club licenses for teams such as Club Carabobo FC, Dynamo Puerto F.C., and Titanes FC.</p><p>COMET player registration files from Club Carabobo FC.</p><p>Tax returns and contracts.</p><p>What specific data was exposed in the COMET files?</p><p>Full names, national ID numbers (cédulas de identidad), phone numbers, email addresses, and home addresses.</p><p>This vulnerability was responsibly reported on April 6 via email and through the official complaints/reporting section on the FVF website. </p><p>The exposed storage was blocked on April 17.</p><p>However, as of today, I have not received any from the FVF.</p><p>In the last few hours I've learned that the FVF is looking for human capital in cybersecurity.</p><p>If this hadn't been reported, it might still have been active and could have put players' data at risk.</p><p><a href="https://infosec.exchange/tags/databreach" rel="tag">#<span>databreach</span></a> <a href="https://infosec.exchange/tags/Venezuela" rel="tag">#<span>Venezuela</span></a> <a href="https://infosec.exchange/tags/cybersecurity" rel="tag">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/incidentresponse" rel="tag">#<span>incidentresponse</span></a></p>

<div class="row mt-3"><div class="col-12 mt-3"><img class="img-thumbnail" src="https://media.infosec.exchange/infosec.exchange/media_attachments/files/116/444/471/662/122/893/original/f48eea8b3e1abac3.png" alt="Link Preview Image" /><img class="img-thumbnail" src="https://media.infosec.exchange/infosec.exchange/media_attachments/files/116/444/471/668/461/416/original/62860425cd44e6b8.png" alt="Link Preview Image" /><img class="img-thumbnail" src="https://media.infosec.exchange/infosec.exchange/media_attachments/files/116/444/471/668/461/417/original/de7bbe8783d2416e.png" alt="Link Preview Image" /><img class="img-thumbnail" src="https://media.infosec.exchange/infosec.exchange/media_attachments/files/116/444/471/676/653/543/original/bb944df8121c9966.png" alt="Link Preview Image" /></div></div>]]></description><link>https://board.circlewithadot.net/topic/28d87a00-0947-464a-8cf2-743ad54bf402/sensitive-data-exposure-at-the-venezuelan-football-federation-fvf</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 04:37:04 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/28d87a00-0947-464a-8cf2-743ad54bf402.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 21 Apr 2026 20:08:30 GMT</pubDate><ttl>60</ttl></channel></rss>