Skip to main content
Exploitation reportedNot in CISA KEV yet

CVE-2026-48611

Exploitation reported by one source. First attested on 2026-07-20 by GCVE · kevintel.

  • Published2026-06-12
  • WeaknessCWE-287

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Improper authentication checks in the OAuth implementation allow account hijacking even when OAuth is not configured or enabled leading to unauthorized access in default installations.

Timeline

dates in UTC
  1. 2026-06-1204:17CVE publishedNVD
  2. 2026-07-2007:57Listed as exploited by GCVEGCVE
  3. 2026-07-2007:57Exploitation first reportedGCVE
  4. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-48611?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-48611?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-48611 yet.

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

read 2026-10-23 19:25 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
2 repositories, unverifiedlxdwnpiper/CVE-2026-48611-phpBBEthicalgrey/phpBB-CVE-2026-48611
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • GCVEexploitation2026-07-20
  • CISA-ADPSSVC decisionnone2026-06-12
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.09.8read 2026-10-23
  • CNAweakness (CWE)CWE-287read 2026-10-23
  • FIRST EPSSEPSS score2.9 %2026-10-22
  • PoC-in-GitHubproof of concept2read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2026-06-12
Last Modified
2026-06-17
NVD status
Deferred

Frequently asked questions

What is CVE-2026-48611?

Improper authentication checks in the OAuth implementation allow account hijacking even when OAuth is not configured or enabled leading to unauthorized access in default installations.

Is CVE-2026-48611 actively exploited?

Active exploitation of CVE-2026-48611 has not been confirmed. Its EPSS score was 2.9% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-48611?

CVE-2026-48611 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month