CVE-2026-48908

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-07-07), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild
9.8EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: 89%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

A vulnerability in SP Page Builder for Joomla allows unauthenticated users to upload arbitrary files, ultimately resulting in the upload and execution of PHP code.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.
EPSS PROB
89%
EPSS %ILE
99th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA 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.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://extensions.joomla.org/extension/sp-page-builder/ · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-48908

Published

June 20, 2026

Last Modified

October 8, 2026

Advisory Details (5)

Auto-updated Oct 8, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). No fix on record yet.
Web page

SP Page Builder - The Best Joomla Drag & Drop Page Builder - JoomShaper

https://www.joomshaper.com/page-builder
Web page

[Locked] [URGENT] Potential Security Vulnerability Identified In SP Page Builder (v6.1.1) - Question | JoomShaper

https://www.joomshaper.com/forum/question/45152
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-48908
Web page

SP Page Builder Zero Day RCE Fixed in 6.6.2 | mySites.guru

https://mysites.guru/blog/sp-page-builder-zero-day-uploadcustomicon-rce/
Web page

SP Page Builder, by JoomShaper - Joomla Extension Directory

https://extensions.joomla.org/extension/sp-page-builder/

Vendor Advisories for CVE-2026-48908(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 44× in last 7d / 209× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 826 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 727 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 03:58 UTCEG score recompute
  2. 2026-10-14 03:58 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-13 05:02 UTCEG score recompute
  4. 2026-10-13 05:02 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-12 16:00 UTCEG score recompute
  6. 2026-10-12 06:07 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-12 01:53 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-11 21:40 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-11 19:43 UTCEG score recompute
  10. 2026-10-11 17:27 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-11 16:58 UTCEG score recompute
  12. 2026-10-11 14:22 UTCEG score recompute
  13. 2026-10-11 13:15 UTCEG score recompute
  14. 2026-10-11 13:14 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-11 08:59 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-11 04:46 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-11 00:33 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-10 20:19 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-10 16:07 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-10 11:54 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-10 07:42 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-10 03:29 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-09 23:17 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-09 19:05 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-09 14:53 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 74 more
  1. 2026-10-09 10:40 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-09 06:25 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-09 02:12 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-08 22:00 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-08 17:48 UTCEG score recompute
  6. 2026-10-08 17:48 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-08 17:12 UTCEPSS rescoreEPSS 89% · 99th percentile
  8. 2026-10-08 13:29 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-08 09:15 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-08 05:02 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-08 03:44 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-07 23:32 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-07 19:19 UTCEG score recompute▼ 0.20
  14. 2026-10-07 19:19 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-07 19:19 UTCNVD updateCVSS v3 → 9.8
  16. 2026-10-07 18:27 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-07 17:15 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-07 13:03 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-07 08:51 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-07 04:39 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-07 00:26 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-06 20:14 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-06 16:02 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-06 11:50 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-06 07:38 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-06 03:26 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-06 03:26 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-06 03:26 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-06 03:25 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-05 23:13 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-05 19:01 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-05 14:49 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-05 10:38 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-05 06:25 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-05 02:13 UTCEG score recompute
  36. 2026-10-05 02:12 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-04 23:22 UTCEPSS rescoreEPSS 89% · 99th percentile
  38. 2026-10-04 21:57 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-04 17:45 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-04 13:32 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-04 09:20 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-04 05:07 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-04 00:55 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-03 20:43 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-03 16:28 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-03 12:17 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-03 08:04 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-03 03:51 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-02 23:39 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-02 19:27 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-02 15:14 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-02 11:02 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-02 06:50 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-02 02:38 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-01 22:24 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-01 18:11 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-01 13:57 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-01 09:45 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-01 05:33 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-10-01 01:21 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-09-30 21:09 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-30 16:57 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-09-30 12:45 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-30 08:33 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-09-30 04:21 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-09-30 00:08 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-09-29 19:54 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-09-29 15:41 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-09-29 11:28 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-09-29 07:16 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-09-29 03:04 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-28 22:51 UTCEG score recompute
  73. 2026-09-28 22:51 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-09-28 18:39 UTCGHSA enrichmentGHSA-8fwr-8fxr-8v2p · GitHub severity CRITICAL · GitHub CVSS 9.8

Publicly available exploits

(6 references)

Public exploit code is referenced for this CVE (4 GitHub PoCs), as are 1 Nuclei detection template, 1 GitHub checker repository. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • GitHub checkeryora1928/CVE-2026-48908-by-yora
    Published Aug 12, 2026

    Passive security checker for CVE-2026-48908 affecting SP Page Builder.

    Open source ↗
  • GitHub PoCimXur/CVE-2026-48908-Joomla-SP-Page-Builder-RCE
    Published Jul 25, 2026

    Technical analysis and advisory for CVE-2026-48908: Unauthenticated Arbitrary File Upload to RCE in JoomShaper SP Page Builder.

    Open source ↗
  • Nucleijavascript/cves/2026/CVE-2026-48908.yaml
    Published Jul 23, 2026

    Joomla SP Page Builder <= 6.6.1 - Unauthenticated Arbitrary File Upload RCE

    Open source ↗
  • GitHub PoCJenderal92/CVE-2026-48908
    Published Jul 7, 2026

    CVE-2026-48908 — PoC exploit for unauthenticated RCE in SP Page Builder (Joomla) via arbitrary file upload. Multi‑threaded, case‑bypass, shell verification. For authorized security testing only.

    Open source ↗
  • GitHub PoC0xBlackash/CVE-2026-48908
    Published Jun 24, 2026

    CVE-2026-48908

    Open source ↗
  • GitHub PoCpapageo75/CVE-2026-48908-PoC
    Published Jun 22, 2026

    Unauthenticated RCE PoC for CVE-2026-48908 — SP Page Builder for Joomla (≤ 6.6.1): arbitrary file upload via asset.uploadCustomIcon. Self-cleaning, token-guarded. Authorized testing only.

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2026-48908?
CVE-2026-48908 is a critical-severity vulnerability; its CVE record was published on June 20, 2026. A vulnerability in SP Page Builder for Joomla allows unauthenticated users to upload arbitrary files, ultimately resulting in the upload and execution of PHP code.
When was the CVE record for CVE-2026-48908 published?
The CVE record for CVE-2026-48908 was published on June 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-48908 actively exploited?
Yes. CISA added CVE-2026-48908 to the Known Exploited Vulnerabilities catalog on July 7, 2026, affecting JoomShaper SP Page Builder. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation, and watch the vendor's advisory for the fix.
What is the CVSS score of CVE-2026-48908?
CVE-2026-48908 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2026-48908?
CVE-2026-48908 affects JoomShaper SP Page Builder.
How do I remediate CVE-2026-48908?
No fix for CVE-2026-48908 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-48908 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-48908

Explore →

Is Your Infrastructure Affected by CVE-2026-48908?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs