{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-12410 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-12410 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-12410 is a medium-severity SQL injection vulnerability in rustaurius Front End Users, published on 2 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-12410 and fix it if it is affected.\n\nWhat it is: CVE-2024-12410 is a medium-severity SQL injection vulnerability in rustaurius Front End Users, published on 2 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-12410 in the wild and no public exploit code.\n\nAffected product: rustaurius Front End Users. 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-2024-12410/ (Markdown: https://insights.sbomify.com/CVE-2024-12410/index.md)","id":"CVE-2024-12410","markdown":"https://insights.sbomify.com/CVE-2024-12410/index.md","name":"CVE-2024-12410","record":{"aliases":["GHSA-qm6q-x38h-hpp4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Attackers can exploit SQL injection in the Front End Users plugin to extract sensitive database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"front_end_users","vendor":"etoilewebdesign"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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 Front End Users plugin for WordPress is vulnerable to SQL Injection via the 'UserSearchField' parameter in all versions up to, and including, 3.2.32 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.","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":"Front End Users \u003c= 3.2.32 - Authenticated (Admin+) SQL injection","id":"CVE-2024-12410","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"WP Ad Guru – Banner ad, Responsive popup, Popup maker, Ad rotator \u0026 More \u003c= 2.5.4 - Reflected Cross-Site Scripting","id":"CVE-2024-12411"},"packages":[],"prev":{"headline":"Simple:Press Forum \u003c= 6.10.11 - Reflected Cross-Site Scripting","id":"CVE-2024-12409"},"products":["Front End Users"],"published":"2025-04-02","related":[{"cvss_score":9.8,"headline":"Front-End-Only-Users \u003c= 3.2.32 - Unauthenticated Arbitrary File Upload","id":"CVE-2025-2005","kev_date_added":null,"published":"2025-04-02"},{"cvss_score":8.8,"headline":"Front End Users \u003c= 3.2.28 - Authenticated (Contributor+) Time-Based SQL Injection","id":"CVE-2024-7607","kev_date_added":null,"published":"2024-08-29"},{"cvss_score":7.1,"headline":"Front End Users \u003c= 3.2.32 - Reflected XSS","id":"CVE-2024-13569","kev_date_added":null,"published":"2025-04-22"},{"cvss_score":7.1,"headline":"WordPress Front End Users plugin \u003c 3.2.25 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2023-33322","kev_date_added":null,"published":"2024-03-26"},{"cvss_score":6.5,"headline":"WordPress Front End Users Plugin \u003c= 3.2.30 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2025-26877","kev_date_added":null,"published":"2025-02-25"},{"cvss_score":6.5,"headline":"WordPress Front End Users Plugin \u003c= 3.2.24 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-34005","kev_date_added":null,"published":"2023-07-17"},{"cvss_score":6.4,"headline":"Front End Users \u003c= 3.2.30 - Authenticated (Contributor+) Stored Cross-Site Scripting via forgot-password Shortcode","id":"CVE-2024-13563","kev_date_added":null,"published":"2025-02-15"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["rustaurius"]},"summary":"Attackers can exploit SQL injection in the Front End Users plugin to extract sensitive database information.","url":"https://insights.sbomify.com/CVE-2024-12410/"}