{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-48771 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-48771 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-48771 is a high-severity vulnerability in Ishankjha740 ishankportfolio, published on 11 Aug 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-48771 and fix it if it is affected.\n\nWhat it is: CVE-2026-48771 is a high-severity vulnerability in Ishankjha740 ishankportfolio, published on 11 Aug 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-48771 in the wild and no public exploit code.\n\nAffected product: Ishankjha740 ishankportfolio. 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-48771/ (Markdown: https://insights.sbomify.com/CVE-2026-48771/index.md)","id":"CVE-2026-48771","markdown":"https://insights.sbomify.com/CVE-2026-48771/index.md","name":"CVE-2026-48771","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Portfolio website","requires_auth":"none","summary":"Attackers can read or modify contact form submissions due to insecure client-side database configuration, exposing PII.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"ishankportfolio is a portfolio website. Prior to version 1.0.1, contact form submissions could potentially be exposed due to improperly secured client-side database configuration and insufficient access control policies. Applications using publicly exposed database credentials or permissive database rules may allow unauthorised users to read, modify, or abuse stored form submission data. This could impact personally identifiable information (PII) submitted through the website contact form, including names, email addresses, phone numbers, and messages. The issue has been patched in version 1.0.1. Users unable to upgrade immediately can reduce risk by disabling public read/write database access, rotating exposed API keys, restricting database policies to authenticated requests only, moving sensitive operations to secure backend/serverless functions, and/or monitoring database activity logs for suspicious access.","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":"ishankportfolio: Stored Contact Form Submission Exposure via Public Client-Side Database Configuration","id":"CVE-2026-48771","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"ProxySQL: PROXY-Protocol-v1 UNKNOWN parses spoofed source IP, bypassing mysql_query_rules.client_addr ACL","id":"CVE-2026-48772"},"packages":[],"prev":{"headline":"Notepad++ WM_COPYDATA COPYDATA_FULL_CMDLINE local DoS crash","id":"CVE-2026-48770"},"products":["ishankportfolio"],"published":"2026-08-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["Ishankjha740"]},"summary":"Attackers can read or modify contact form submissions due to insecure client-side database configuration, exposing PII.","url":"https://insights.sbomify.com/CVE-2026-48771/"}