{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1291 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1291 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1291 is a high-severity SQL injection vulnerability in Apache Fineract, published on 20 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1291 and fix it if it is affected.\n\nWhat it is: CVE-2018-1291 is a high-severity SQL injection vulnerability in Apache Fineract, published on 20 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1291 in the wild and no public exploit code.\n\nAffected product: Apache Fineract. 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-2018-1291/ (Markdown: https://insights.sbomify.com/CVE-2018-1291/index.md)","id":"CVE-2018-1291","markdown":"https://insights.sbomify.com/CVE-2018-1291/index.md","name":"CVE-2018-1291","record":{"aliases":["GHSA-7wqp-wr74-cqv2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Fineract","requires_auth":"low_privilege","summary":"Attackers can inject SQL via the orderBy parameter to read or modify unauthorized data in Apache Fineract.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"fineract","vendor":"apache"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Apache Fineract 1.0.0, 0.6.0-incubating, 0.5.0-incubating, 0.4.0-incubating exposes different REST end points to query domain specific entities with a Query Parameter 'orderBy' which are appended directly with SQL statements. A hacker/user can inject/draft the 'orderBy' query parameter by way of the \"order\" param in such a way to read/update the data for which he doesn't have authorization.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SQL injection in Apache Fineract","id":"CVE-2018-1291","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in Apache Fineract","id":"CVE-2018-1292"},"packages":[],"prev":{"headline":"SQL injection in Apache Fineract","id":"CVE-2018-1290"},"products":["Apache Fineract"],"published":"2018-04-20","related":[{"cvss_score":9.9,"headline":"SQL injection in Apache Fineract","id":"CVE-2024-23538","kev_date_added":null,"published":"2024-03-29"},{"cvss_score":9.8,"headline":"SQL injection in Apache Fineract","id":"CVE-2018-11800","kev_date_added":null,"published":"2019-06-11"},{"cvss_score":9.8,"headline":"SQL injection in Apache Fineract","id":"CVE-2018-11801","kev_date_added":null,"published":"2019-06-11"},{"cvss_score":9.8,"headline":"SQL injection in Apache Fineract","id":"CVE-2018-1290","kev_date_added":null,"published":"2018-04-20"},{"cvss_score":9.4,"headline":"Apache Fineract: SQL injection vulnerabilities in offices API endpoint","id":"CVE-2024-32838","kev_date_added":null,"published":"2025-02-12"},{"cvss_score":9.1,"headline":"Apache Fineract: Server Key not masked","id":"CVE-2025-58130","kev_date_added":null,"published":"2025-12-12"},{"cvss_score":8.8,"headline":"Apache Fineract: SQL injection in runreports endpoint","id":"CVE-2026-35152","kev_date_added":null,"published":"2026-07-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Apache Software Foundation"]},"summary":"Attackers can inject SQL via the orderBy parameter to read or modify unauthorized data in Apache Fineract.","url":"https://insights.sbomify.com/CVE-2018-1291/"}