{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3057 exists.","fix":"No fix has been published for CVE-2026-3057 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3057 is a medium-severity SQL injection vulnerability in a54552239 pearProjectApi, published on 24 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3057 and fix it if it is affected.\n\nWhat it is: CVE-2026-3057 is a medium-severity SQL injection vulnerability in a54552239 pearProjectApi, published on 24 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3057 exists.\n\nAffected product: a54552239 pearProjectApi. 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-2026-3057/ (Markdown: https://insights.sbomify.com/CVE-2026-3057/index.md)","id":"CVE-2026-3057","markdown":"https://insights.sbomify.com/CVE-2026-3057/index.md","name":"CVE-2026-3057","record":{"aliases":["GHSA-xqg5-5x64-93r9"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"pearProjectApi backend","requires_auth":"low_privilege","summary":"Remote attackers can exploit SQL injection in the dateTotalForProject function to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"pearprojectapi","vendor":"a54552239"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"A security flaw has been discovered in a54552239 pearProjectApi up to 2.8.10. Affected is the function dateTotalForProject of the file application/common/Model/Task.php of the component Backend Interface. The manipulation of the argument projectCode results in sql injection. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"a54552239 pearProjectApi Backend Task.php dateTotalForProject sql injection","id":"CVE-2026-3057","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Information disclosure in Seraphinite Accelerator","id":"CVE-2026-3058"},"packages":[],"prev":{"headline":"Seraphinite Accelerator \u003c= 2.28.14 - Missing Authorization to Authenticated (Subscriber+) Log Clearing","id":"CVE-2026-3056"},"products":["pearProjectApi"],"published":"2026-02-24","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-27112","kev_date_added":null,"published":"2025-01-21"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-27113","kev_date_added":null,"published":"2025-01-21"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-24","vendors":["a54552239"]},"summary":"Remote attackers can exploit SQL injection in the dateTotalForProject function to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2026-3057/"}