{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-24199 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-24199 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-24199 is a medium-severity SQL injection vulnerability in wpDataTables – Tables \u0026 Table Charts, published on 12 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-24199 and fix it if it is affected.\n\nWhat it is: CVE-2021-24199 is a medium-severity SQL injection vulnerability in wpDataTables – Tables \u0026 Table Charts, published on 12 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-24199 in the wild and no public exploit code.\n\nAffected product: wpDataTables – Tables \u0026 Table Charts. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-24199/ (Markdown: https://insights.sbomify.com/CVE-2021-24199/index.md)","id":"CVE-2021-24199","markdown":"https://insights.sbomify.com/CVE-2021-24199/index.md","name":"CVE-2021-24199","record":{"aliases":["GHSA-43mj-v3cx-q3x2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Low-privilege users can exploit blind SQL injection to read database data and potentially take over the WordPress application.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wpdatatables","vendor":"tms-outsource"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The wpDataTables – Tables \u0026 Table Charts premium WordPress plugin before 3.4.2 allows a low privilege authenticated user to perform Boolean-based blind SQL Injection in the table list page on the endpoint /wp-admin/admin-ajax.php?action=get_wdtable\u0026table_id=1, on the 'start' HTTP POST parameter. This allows an attacker to access all the data in the database and obtain access to the WordPress application.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"wpDataTables \u003c 3.4.2 - Blind SQL Injection via start Parameter","id":"CVE-2021-24199","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"wpDataTables \u003c 3.4.2 - Blind SQL Injection via length Parameter","id":"CVE-2021-24200"},"packages":[],"prev":{"headline":"wpDataTables \u003c 3.4.2 - Improper Access Control leading to Table Data Deletion","id":"CVE-2021-24198"},"products":["wpDataTables – Tables \u0026 Table Charts"],"published":"2021-04-12","related":[{"cvss_score":8.1,"headline":"wpDataTables \u003c 3.4.2 - Improper Access Control leading to Table Permission Takeover","id":"CVE-2021-24197","kev_date_added":null,"published":"2021-04-12"},{"cvss_score":8.1,"headline":"wpDataTables \u003c 3.4.2 - Improper Access Control leading to Table Data Deletion","id":"CVE-2021-24198","kev_date_added":null,"published":"2021-04-12"},{"cvss_score":7.2,"headline":"wpDataTables \u003c 2.1.66 - Admin+ PHP Object Injection","id":"CVE-2023-4314","kev_date_added":null,"published":"2023-09-11"},{"cvss_score":6.5,"headline":"WordPress wpDataTables Plugin \u003c= 2.1.49 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-23876","kev_date_added":null,"published":"2023-05-03"},{"cvss_score":6.5,"headline":"wpDataTables \u003c 3.4.2 - Blind SQL Injection via length Parameter","id":"CVE-2021-24200","kev_date_added":null,"published":"2021-04-12"},{"cvss_score":6.1,"headline":"wpDataTables – WordPress Data Table, Dynamic Tables \u0026 Table Charts Plugin \u003c= 3.4.2.2 - Reflected Cross-Site Scripting.","id":"CVE-2024-0591","kev_date_added":null,"published":"2024-03-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["wpDataTables"]},"summary":"Low-privilege users can exploit blind SQL injection to read database data and potentially take over the WordPress application.","url":"https://insights.sbomify.com/CVE-2021-24199/"}