SQL Injection

Every one of the 10 is a mark on the map. Named now: 1 to 10, most at risk first.

1. phpMyFAQ <= 4.1.1 - SQL InjectionCVE-2026-46364thorsten · CVSS 9.8 · 1.7% likely

   CWE-89

2. phpMyFAQ SQL Injection at "Save News"CVE-2024-27299thorsten · CVSS 8.8 · 1.2% likely

   CWE-89

3. phpMyFAQ SQL injections at insertentry & saveentryCVE-2024-28107thorsten · CVSS 8.8 · 1.0% likely

   CWE-89

4. phpMyFAQ has Authenticated SQL Injection in Configuration Update FunctionalityCVE-2025-62519thorsten · CVSS 7.2 · 0.8% likely

   CWE-89

5. phpMyFAQ before 4.1.7 SQL Injection via GlossaryCVE-2026-76205thorsten · CVSS 8.1 · 0.4% likely

   CWE-89

6. phpMyFAQ has a LIKE Wildcard Injection in Search.php — Unescaped % and _ Metacharacters Enable Broad Content DisclosureCVE-2026-34973thorsten · CVSS 6.9 · 0.3% likely

   CWE-943

7. phpMyFAQ before 4.1.9 SQL Injection via api/autocomplete Search EndpointCVE-2026-109573thorsten · CVSS 8.1 · 0.3% likely

   CWE-89

8. phpMyFAQ - SQL Injection in CurrentUser::setTokenData via Unescaped OAuth Token FieldsCVE-2026-46359thorsten · CVSS 7.5 · 0.3% likely

   CWE-89

9. phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word InsertionCVE-2026-56738thorsten · CVSS 8.5 · 0.3% likely

   CWE-89

10. phpMyFAQ: SQL LIKE Wildcard Injection in Chat User Search Allows Authenticated User EnumerationCVE-2026-47132thorsten · CVSS 5.4 · 0.3% likely

    CWE-89

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.