CVE-2026-48771
Received Received - Intake

Information Disclosure in Ishankportfolio Contact Form

Publication date: 2026-08-11

Last updated on: 2026-08-11

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-11
Last Modified
2026-08-11
Generated
2026-08-11
AI Q&A
2026-08-11
EPSS Evaluated
N/A
NVD
CVE-2026-48771
EUVD
EUVD-2026-56785

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
ishankportfolio ishankportfolio to 1.0.1 (exc)
ishankjha740 ishankportfolio-contact-form to 1.0.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the ishankportfolio website where contact form submissions could be exposed due to insecure client-side database settings and weak access controls. Attackers could exploit this to read, modify, or misuse sensitive data like names, emails, phone numbers, and messages submitted via the contact form.

Detection Guidance

Check for publicly exposed database credentials or permissive database rules in your ishankportfolio configuration. Review database access logs for unauthorized read/write operations. Inspect network traffic for unencrypted contact form submissions to external databases.

Impact Analysis

If you use a vulnerable version of ishankportfolio, your contact form data including personally identifiable information (PII) could be accessed by unauthorized parties. This may lead to data breaches, identity theft, or misuse of submitted information. The impact is higher if the database is publicly accessible or has weak access policies.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR and HIPAA due to unauthorized exposure of personally identifiable information (PII). GDPR requires protecting personal data, and HIPAA mandates safeguarding health-related information. A breach could result in legal penalties, fines, and reputational damage for organizations handling sensitive data.

Mitigation Strategies

Upgrade to version 1.0.1 or later. Disable public database access and rotate exposed API keys. Restrict database policies to authenticated requests only. Move sensitive operations to secure backend functions. Monitor database activity logs for suspicious access.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-48771. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart