top of page

Three Old Bugs Got Fresh Exploitation Flags This Week: ThinkPHP 5.0, a TOTOLINK Router and a Django SQL Injection. If You Still Run Any of Them, Here Is the Fix

Writer: Patrick Duggan
Patrick Duggan
3 minutes ago
4 min read

What to do first. Three bugs between three and seven years old showed up this week in VulnCheck's catalog of exploited vulnerabilities with new dates, each flagged as seen by VulnCheck's own canaries. None of them is new, and that is the point: they are still being tried because old installs are still out there. If you run any of these, act today.


  • ThinkPHP 5.0 below 5.0.24: upgrade, or move off the 5.0 line entirely (it is long out of support). Until then, block POST requests whose body contains _method=__construct at your web server or WAF.

  • TOTOLINK A3300R router, firmware V17.0.0cu.557_B20221024: check the TOTOLINK support site for newer firmware for your model. If there is none, replace the router. At minimum, make sure its admin page is not reachable from the internet.

  • Django 1.11 below 1.11.28, 2.2 below 2.2.10, 3.0 below 3.0.3: upgrade to a supported Django release. All three of those lines are end of life.


What each bug does


ThinkPHP, CVE-2019-25782 (CVSS 9.8). This is the well-known ThinkPHP 5.0.x remote code execution flaw, only now given its own CVE number (NVD published the record on November 18, 2026). Per the NVD description, an attacker with no account sends a POST request with _method=__construct to overwrite the request filter, then runs system commands through endpoints such as ?s=captcha. NVD's record says exploitation evidence was "first observed by the Shadowserver Foundation on 2023-10-14". Botnets have mass-scanned for this bug for years; a new CVE number makes it visible to tools that only track CVEs.


TOTOLINK A3300R, CVE-2023-37170 (CVSS 9.8). Unauthenticated remote code execution through the lang parameter of the setLanguageCfg function, per NVD (published July 2023). Consumer and small-office routers with flaws like this are where botnets recruit.


Django, CVE-2020-7471 (CVSS 9.8). SQL injection, but only in a narrow case: an application that passes user-supplied text as the delimiter to the PostgreSQL StringAgg aggregate, for example a "download as delimited rows" feature that lets the user pick the separator. Most Django sites never do that. If yours runs one of the old versions above and has such a feature, assume the database can be read.



How sure is the exploitation?


One source. All three were flagged by VulnCheck's canaries; we could not read the sighting details behind the flags. None of the three is in CISA's KEV catalog (checked November 19, 2026). The ThinkPHP bug has the most outside support, through the Shadowserver observation NVD cites. For the Django flaw we have nothing beyond VulnCheck's flag, and the narrow conditions make wide exploitation unlikely; patch it anyway, because the affected versions are years out of support.



What our own sensors can and cannot say


  • TOTOLINK: we checked our edge blocks (567,844 since October 21), edge trap hits (96,597) and origin honeypot (688) for requests to the router's cstecgi.cgi handler. Zero. We run no trap for TOTOLINK devices, so that zero means our sites were not targeted, not that nobody is scanning routers.

  • ThinkPHP: we cannot answer from the edge. The ThinkPHP request is identified by its query string and POST body, and our edge records keep the path without the query string: a test pattern matching any query string found 0 matches across the edge records and 27 in the origin honeypot, which does keep them. So an edge zero for ?s=captcha would be a blind spot, not a measurement, and we report none.

  • Django: this flaw lives inside particular application features; no edge sensor can see it.


Am I affected? A self-check


  • ThinkPHP: look for thinkphp/base.php or the THINK_VERSION constant in your project. Any version starting 5.0 and below 5.0.24 is affected. In web logs, look for POST requests to ?s=captcha or ?s=index/index/index.

  • TOTOLINK: the firmware version is on the router's status page. If it reads V17.0.0cu.557_B20221024 or earlier on an A3300R, it is affected. Check whether the admin page answers on your public IP address from outside your network.

  • Django: run pip show django on the server, and search your code for StringAgg( to see whether any call passes a delimiter that comes from the request.


Indicators


None published in the sources we read. NVD and VulnCheck's catalog list no attacker IP addresses, domains or hashes for these entries, so we added nothing to the feed. Our "Am I affected?" site checker does not apply: these are server and device flaws, not scripts loaded on a homepage.



Sources


  • NVD, CVE-2019-25782: https://nvd.nist.gov/vuln/detail/CVE-2019-25782

  • NVD, CVE-2023-37170: https://nvd.nist.gov/vuln/detail/CVE-2023-37170

  • NVD, CVE-2020-7471: https://nvd.nist.gov/vuln/detail/CVE-2020-7471

  • VulnCheck KEV (canary-flagged entries, read through our daily gap list on November 19, 2026): https://vulncheck.com/kev

  • CISA KEV JSON (checked November 19, 2026: none of the three listed)


Get exploited-bug coverage and a blocklist you can pull for free: register for the DugganUSA feed (docs at docs.dugganusa.com).




Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.


Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page