{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25238 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25238 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25238 is a critical SQL injection vulnerability in pearweb, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25238 and fix it if it is affected.\n\nWhat it is: CVE-2026-25238 is a critical SQL injection vulnerability in pearweb, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25238 in the wild and no public exploit code.\n\nAffected product: pearweb. 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-25238/ (Markdown: https://insights.sbomify.com/CVE-2026-25238/index.md)","id":"CVE-2026-25238","markdown":"https://insights.sbomify.com/CVE-2026-25238/index.md","name":"CVE-2026-25238","record":{"aliases":["GHSA-cv3c-27h5-7gmv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PEAR PHP framework","requires_auth":"none","summary":"Attackers can inject SQL via crafted email values in bug subscription deletion, potentially reading or modifying data in PEAR.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pearweb","vendor":"pear"}],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"PEAR is a framework and distribution system for reusable PHP components. Prior to version 1.33.0, a SQL injection vulnerability in bug subscription deletion may allow attackers to inject SQL via a crafted email value. This issue has been patched in version 1.33.0.","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":"PEAR is Vulnerable to SQL Injection in Bug Subscription Deletion via Weak Email Validation","id":"CVE-2026-25238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"PEAR is Vulnerable to SQL Injection in apidoc_queue Insert via Unescaped Filename","id":"CVE-2026-25239"},"packages":[],"prev":{"headline":"PEAR is Vulnerable to PHP Code Execution via preg_replace /e in Bug Update Emails","id":"CVE-2026-25237"},"products":["pearweb"],"published":"2026-02-03","related":[{"cvss_score":9.3,"headline":"PEAR is Vulnerable to SQL Injection in /get/\u003cpackage\u003e/\u003cversion\u003e Endpoint","id":"CVE-2026-25241","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":9.2,"headline":"PEAR is Vulnerable to PHP Code Execution via preg_replace /e in Bug Update Emails","id":"CVE-2026-25237","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":8.2,"headline":"PEAR Has a Predictable Verification Hash in Election Account Requests","id":"CVE-2026-25235","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":8.2,"headline":"PEAR is Vulnerable to SQL Injection in apidoc_queue Insert via Unescaped Filename","id":"CVE-2026-25239","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":7.1,"headline":"PEAR Has a Roadmap Authorization Bypass via Operator Precedence Bug","id":"CVE-2026-25233","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":6.9,"headline":"PEAR is Vulnerable to SQL Injection in Damblan_Karma IN() Query via Literal Substitution","id":"CVE-2026-25236","kev_date_added":null,"published":"2026-02-03"}],"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":"total"},"state":"PUBLISHED","updated":"2026-02-04","vendors":["pear"]},"summary":"Attackers can inject SQL via crafted email values in bug subscription deletion, potentially reading or modifying data in PEAR.","url":"https://insights.sbomify.com/CVE-2026-25238/"}