CVE-2026-48939
Exploitation confirmed. First attested on 2026-07-10 by CISA-ADP, CISA KEV, GCVE · kevintel.
- Published2026-06-20
- Fixed in4.0.8 · 3.9.15
- WeaknessCWE-434
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « 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
A vulnerability in the iCagenda extension for Joomla allows the upload of arbitrary files in the file attachment feature, ultimately resulting in PHP code upload and execution.
Timeline
dates in UTC- 2026-06-2013:16CVE publishedNVD
- 2026-07-10Listed as exploited by GCVEGCVE
- 2026-07-10Exploitation first reportedCISA KEV
- 2026-07-10Added to the CISA KEV catalogCISA KEV
- 2026-07-1017:37SSVC exploitation set to activeCISA-ADP
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-48939?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-48939?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.0 | ≥ 4.0.0, < 4.0.8 | 4.0.8 | NVD |
| 3.x | ≥ 3.2.1, < 3.9.15 | 3.9.15 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Joomlic icagenda to 4.0.8 · 3.9.15
- CISA’s required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.due 2026-07-13
Advisories and patches
- www.icagenda.comRelease Notes
- www.icagenda.comRelease Notes
Detection
read 2026-10-23 19:25 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 3 repositories, unverifiedPolosss/By-Poloss..-..CVE-2026-48939shinthink/CVE-2026-48939ChiefYoru/CVE-2026-48939_PoC PoC-in-GitHub
CISA Known Exploited Vulnerability
- Date Added
- 2026-07-10
- Patch Due Date
- 2026-07-13
- Ransomware Use
- Unknown
- Required Action
- Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Sources
- CISA KEVKEV entry2026-07-10
- GCVEexploitation2026-07-10
- CISA-ADPSSVC decisionactive2026-07-10
- OpenCVESSVC decisionactive—
- CNACVSS 4.010read 2026-10-23
- NVDCVSS 3.19.8read 2026-10-23
- CNAweakness (CWE)CWE-434read 2026-10-23
- NVDweakness (CWE)CWE-434read 2026-10-23
- FIRST EPSSEPSS score20.1 %read 2026-10-23
- PoC-in-GitHubproof of concept3read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CVSS 4.0 vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:A/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:X/U:Red
- Published
- 2026-06-20
- Last Modified
- 2026-07-11
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2026-48939?
Is CVE-2026-48939 actively exploited?
What is the CVSS score for CVE-2026-48939?
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
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.