CVE-2026-48771

ishankportfolio: Stored Contact Form Submission Exposure via Public Client-Side Database Configuration

Published Aug 11, 2026 CVSS 3.1 · 8.2 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

This vulnerability allows unauthorized individuals to read, modify, or abuse stored contact form submissions in the Ishankportfolio website. The issue arises from an improperly secured client‑side database configuration and insufficient access control policies that, when coupled with publicly exposed database credentials or permissive rules, permit attackers to access PII such as names, email addresses, phone numbers, and messages. The impact is a breach of confidentiality and potential misuse of personal information.

Affected Systems

Products impacted are Ishankjha740’s ishankportfolio prior to version 1.0.1. The fix is incorporated in 1.0.1. Any deployment that uses a publicly exposed client‑side database or exposes credentials without restricting access falls into this category.

Risk and Exploitability

The CVSS score of 8.2 classifies the vulnerability as high severity. The EPSS score of less than 1% indicates a low to very low probability of exploitation, and the solution has not been listed in the CISA KEV catalog. Attackers could exploit the flaw by targeting the public web interface that exposes the database, using exposed credentials or permissive rules to read or alter data. Since the issue is mitigated by upgrading to 1.0.1, organizations should assess whether the database access configuration respects the principle of least privilege.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to ishankportfolio 1.0.1 to apply the vendor patch
  • Disable or restrict public read/write access to the client‑side database, ensuring only authenticated requests can access the data store
  • Rotate any exposed API keys or credentials that grant database access
  • Move any sensitive handling of form submissions to a secure backend or serverless function and monitor database activity logs for suspicious activity

Generated by OpenCVE AI on August 12, 2026 at 20:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Ishankjha740
Ishankjha740 ishankportfolio
Vendors & Products Ishankjha740
Ishankjha740 ishankportfolio
Type Values Removed Values Added
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.
Title ishankportfolio: Stored Contact Form Submission Exposure via Public Client-Side Database Configuration
Weaknesses CWE-200
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 13, 2026, 3:55 PM
Reserved
May 22, 2026, 7:39 PM
Status
Deferred
Published
Aug 11, 2026, 6:17 PM
Modified
Oct 23, 2026, 9:10 PM