Developer Exposes 12 Vulnerabilities in FastAPI Todo App After 176 Bots Bypass Protections
A Russian developer who started with a simple FastAPI todo list four months ago ended up running a multi-product platform and uncovering a dozen security issues after bots flooded the registration form.
The service at getdoday.ru grew to include a planner for schoolchildren, a Q&A module, a traffic-ticket trainer, and a tutor dashboard, all inside one 86,000-line monolith with 1,325 tests. Within two weeks the database showed 238 new accounts; only 62 confirmed their email. The remaining 176 were bots using disposable domains such as sdffsd.sdd and prweorwef.com.
Bots bypassed three protection layers
The original defenses were a honeypot field, a five-registrations-per-minute IP limit, and email confirmation. None worked. The rate limiter used an in-memory deque that was cleared on every deployment; with dozens of commits per day the counter effectively never existed. uvicorn was started with --forwarded-allow-ips='*', causing it to trust the leftmost IP supplied in the X-Forwarded-For header. An attacker could therefore rotate a fake address on every request and never hit the limit. Email verification set a timestamp but the column was never checked anywhere in the authorization logic.
Instead of adding hard email gates that would hurt real users behind school NATs, the developer implemented three lightweight checks: a signed timestamp proving the form was rendered at least a few seconds earlier, hourly registration counters stored in the database with separate per-subnet limits, and a DNS lookup confirming the mail domain actually exists.
Stored XSS via JSON-LD and an IDOR
During the subsequent full audit twelve additional vulnerabilities were found. Public Q&A pages rendered user-supplied question titles inside a JSON-LD script block using the safe filter. Because the HTML parser does not understand JSON, an attacker could close the script tag and inject executable code that exfiltrated the victim’s entire account export.
Another flaw allowed any logged-in user to read every task belonging to a project simply by supplying its UUID to the /api/tasks endpoint; membership checks existed only on the HTML page, not inside the service layer.
Other issues included an inability to invalidate sessions after password change and rate-limit bypasses on multiple endpoints. All findings were addressed with tests and the developer published the complete post-mortem on Habr.
Related articles
Managing Bug Bounty Programs: Handling Report Overload, Duplicates, and AI-Generated Submissions
Launching a bug bounty program is only the beginning; the real challenge lies in managing the influx of reports, filtering duplicates and AI-generated noise, and ensuring vulnerabilities are actually fixed. Standoff Bug Bounty recommends starting with private programs limited to 30-50 researchers to build internal processes before scaling. Companies like Flavau developed custom DevSecOps consoles that cut report triage time by a factor of 10 by automating duplicate detection and assignee assignment. The platform introduced neural slop windows that limit submissions based on researcher quality history, addressing the surge in AI-generated invalid reports observed in spring 2026. Fixed response timelines, clear ownership roles, and prioritized remediation of critical issues help maintain program effectiveness. Google’s decision to pause its OSS VRP in October 2026 due to automated report floods highlights broader industry concerns, yet experts maintain that human-driven independent validation remains essential. Key success metrics include reduced risk from fixed high-severity issues, lower average payout costs, and improved cross-team communication between security and development.
Researcher Bypasses Safe Exam Browser Checks in Moodle Using MITM Proxy and Canonical Config Key Hash
A detailed technical write-up describes how a student bypassed the proprietary Safe Exam Browser requirement for Moodle quizzes by reverse-engineering the single-header authentication mechanism. The bypass relies on fetching the public SEB configuration XML from the open endpoint, computing a canonical SHA256 hash known as ConfigKey, and injecting the resulting X-SafeExamBrowser-ConfigKeyHash header via mitmproxy. Moodle caches a successful check inside the PHP session, allowing all subsequent requests to be made from a normal browser without further header manipulation. Two implementations were created: a headless Python client for full automation of quizzes and a transparent mitmproxy addon that lets a user continue interacting with the test manually. The author also handled edge cases such as crossword OCR with Tesseract, dynamic qubaid and sequencecheck values on retakes, and audio listening sections. The resulting scores reached 772 out of 780 points, placing the account 22nd out of 372 students. The full code, including configkey.py, mitm_addon.py and unit tests, has been published under CC BY-NC-SA 4.0.
Oracle Releases 655 Security Patches in November 2026 Critical Update
Oracle has published its November 2026 Critical Security Patch Update, delivering a total of 655 patches that address vulnerabilities across a wide range of products. The update resolves 640 unique CVEs after accounting for duplicates and supplements the regular quarterly Critical Patch Update. Affected products include Oracle Database Server, Oracle Java SE, MySQL Server, Oracle WebLogic Server, Oracle E-Business Suite, and Oracle VM VirtualBox. Among the fixes, Oracle Hyperion accounts for the largest share with 267 patches, followed by Oracle Supply Chain with 74 and both Oracle Fusion Middleware and Oracle E-Business Suite with 71 each. Of the vulnerabilities patched, 311 carry a CVSSv3.1 base score of 7.0 or higher, including 62 rated 9.0 or above, while 303 can be exploited remotely.
DPoP Enforcement Failure Allows Bearer Token Bypass in redb.Identity OpenID Server
A vulnerability in redb.Identity allowed DPoP-bound access tokens to be accepted without proof-of-possession on the /connect/userinfo and management API endpoints. The flaw affected versions 1.0.1 through 4.6.1 when DPoP was enabled and was assigned GHSA-vmj2-8phj-mfxf with a CVSS 3.1 score of 7.4. External researcher Rathnadeepan reported the issue privately on 4 November, enabling a same-day confirmation and a fix released in 4.6.2 just one day later. Existing test suites, including over 2,000 green tests across three databases, failed to catch the problem because they only verified positive cases and never tested rejection of missing or invalid DPoP proofs. The root cause traced back to endpoints that only inspected the Bearer scheme and an earlier OpenIddict migration change that disabled cnf validation for jkt-bound tokens. The project published the advisory without waiting for a CVE and added negative test cases plus demo scenarios to prevent similar gaps in the future.