{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-0410 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-0410 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-0410 is a high-severity SQL injection vulnerability in Unknown WP Visitor Statistics (Real Time Traffic), published on 7 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-0410 and fix it if it is affected.\n\nWhat it is: CVE-2022-0410 is a high-severity SQL injection vulnerability in Unknown WP Visitor Statistics (Real Time Traffic), published on 7 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-0410 in the wild and no public exploit code.\n\nAffected product: Unknown WP Visitor Statistics (Real Time Traffic). 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-2022-0410/ (Markdown: https://insights.sbomify.com/CVE-2022-0410/index.md)","id":"CVE-2022-0410","markdown":"https://insights.sbomify.com/CVE-2022-0410/index.md","name":"CVE-2022-0410","record":{"aliases":["GHSA-hgrv-3cp5-97qg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated users can exploit SQL injection in the WP Visitor Statistics plugin to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"visitor_statistics","vendor":"codepress"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The WP Visitor Statistics (Real Time Traffic) WordPress plugin before 5.6 does not sanitise and escape the id parameter before using it in a SQL statement via the refUrlDetails AJAX action, available to any authenticated user, leading to a SQL injection","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":"WP Visitor Statistics (Real Time Traffic) \u003c 5.6 - Subscriber+ SQL Injection","id":"CVE-2022-0410","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Asgaros Forum \u003c 2.0.0 - Subscriber+ Blind SQL Injection","id":"CVE-2022-0411"},"packages":[],"prev":{"headline":"Unrestricted Upload of File with Dangerous Type in star7th/showdoc","id":"CVE-2022-0409"},"products":["WP Visitor Statistics (Real Time Traffic)"],"published":"2022-03-07","related":[{"cvss_score":9.8,"headline":"WP Visitor Statistics (Real Time Traffic) \u003c 6.9 - Unauthenticated SQLi","id":"CVE-2023-0600","kev_date_added":null,"published":"2023-05-15"},{"cvss_score":9.3,"headline":"WordPress WP Visitor Statistics plugin \u003c= 5.7 - Multiple Unauthenticated SQL Injection (SQLi) vulnerabilities","id":"CVE-2022-33965","kev_date_added":null,"published":"2022-07-25"},{"cvss_score":8.8,"headline":"WP Visitor Statistics (Real Time Traffic) \u003c 4.8 - Subscriber+ SQL Injection","id":"CVE-2021-24750","kev_date_added":null,"published":"2021-12-21"},{"cvss_score":5.4,"headline":"WP Visitor Statistics (Real Time Traffic) \u003c 6.5 - Contributor+ Stored XSS via Shortcode","id":"CVE-2022-4656","kev_date_added":null,"published":"2023-02-13"},{"cvss_score":5.4,"headline":"WP Visitor Statistics (Real Time Traffic) \u003c 5.5 - Arbitrary IP Address Exclusion to Stored XSS","id":"CVE-2021-25042","kev_date_added":null,"published":"2022-02-28"},{"cvss_score":5.3,"headline":"WordPress WP Stats Manager plugin \u003c= 6.9.4 - Sensitive Data Exposure vulnerability","id":"CVE-2024-24867","kev_date_added":null,"published":"2024-03-17"}],"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-02","vendors":["Unknown"]},"summary":"Authenticated users can exploit SQL injection in the WP Visitor Statistics plugin to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2022-0410/"}