Skip to main content
VulnerabilityPublished Updated

CVE-2026-48771: Ishankjha740 ishankportfolio · Information Exposure

Affects Ishankjha740 ishankportfolioSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 1.0.1 soon.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade ishankportfolio and ishankjha740/ishankportfolio to 1.0.1.

Affected software

ProductAffectedFixed in
Ishankjha740ishankportfolioAffected
  • <1.0.1
Fixed in
  • 1.0.1
GitHubishankjha740/ishankportfoliopkg:github/ishankjha740/ishankportfolioOther threatsAffected
  • <1.0.1
Fixed in
  • 1.0.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in version 1.0.1. Users should upgrade to this version to resolve the vulnerability. For those unable to upgrade immediately, recommended mitigations include disabling public read/write access to the database, rotating any exposed API keys, restricting database access policies to authenticated requests only, moving sensitive operations to secure backend or serverless functions, and monitoring database activity logs for suspicious access.

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.

References

Community reviews

Loading reviews…