Researchers who have responsibly disclosed security issues affecting centralfloridaadu.com are recognized below. Coordinated disclosure is a real contribution to a small operation like this one, and we credit the people who do it well — clear reproduction steps, demonstrated impact, and no public posting before resolution.
2026
No acknowledgments yet. As reports come in and reach resolution, researchers will be listed here.
How to be listed
Report a vulnerability under our disclosure policy. With your consent, we will list your name or handle, the date of disclosure, and a brief description of the issue category. Specifics are withheld until any active risk is mitigated.
Acknowledgments are reserved for confirmed, reproducible findings with demonstrated impact — XSS, broken access control, server-side template injection, exposed credentials, IDOR, or comparable issues. We don’t acknowledge automated scanner output without manual validation, missing security headers without demonstrated impact, or reports based on theoretical risk without an exploit path. The full out-of-scope list is in the disclosure policy.
We will not list anyone without their explicit permission. Researchers who decline public credit are still thanked privately. We do not currently offer monetary bug bounties, though that may change as the site grows — that’s a decision we’d make publicly, with notice.