dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-65877

HIGH · 8.2 CVSS v4.0 Published 2026-07-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable Zero-click 3 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Joomla Extension - joomshaper.com - Authenticated SQL injection in SP Page Builder < 6.7.1 - Improper validation of various parameters in the media manager search and date filters lead to an SQL injection vector.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authenticated SQL injection vulnerability in SP Page Builder (< 6.7.1) Joomla extension. Improper validation of parameters in the media manager's search and date filters allows authenticated attackers to inject malicious SQL queries, potentially leading to unauthorized data access or manipulation.

MitigationUpgrade SP Page Builder to version 6.7.1 or later to obtain the patched code with proper parameter validation. Since this is an authenticated vector, also review and limit user accounts with access to the media manager functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/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:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SP Page Builder extension is installed
    Navigate to Joomla administrator panel, go to Components > SP Page Builder, or check the #__extensions database table for com_sppagebuilder
    Affected if SP Page Builder extension is not found in the Joomla installation
  2. Identify installed SP Page Builder version
    In Joomla admin, go to Components > SP Page Builder > Dashboard, or inspect the manifest file at /administrator/components/com_sppagebuilder/sppagebuilder.xml for the <version> tag
    Affected if The version is lower than 6.7.1 (for example, 6.7.0, 6.6.x, etc.)
  3. Verify media manager component is accessible
    Log into Joomla admin panel and navigate to Components > SP Page Builder > Media Manager. Confirm the media manager interface loads and is functional.
    Affected if The media manager is accessible and functional for the authenticated user account
  4. Inspect media manager request parameters
    Use browser developer tools or a proxy to capture a request when using the search box or date filter in the media manager. Examine the request parameters sent to the backend.
    Affected if The search or date filter parameters are present in the request without proper SQL parameterization indicators (prepared statements)
  5. Check for signs of SQL injection exploitation
    Review web server access logs and Joomla database for suspicious SQL patterns in requests to /index.php?option=com_sppagebuilder&task=media. Search for common SQL injection payloads like UNION SELECT, SLEEP(), or benchmark().
    Affected if Evidence of malicious SQL queries in logs or unexpected data/modifications in the database

The environment is affected if SP Page Builder is installed with a version lower than 6.7.1 and the media manager component is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SP Page Builder to version 6.7.1 or later to obtain the patched code with proper parameter validation. Since this is an authenticated vector, also review and limit user accounts with access to the media manager functionality.

Recommended fix Moderate confidence

SP Page Builder 6.7.1 or later

  1. 1. Log in to the Joomla administrator dashboard
  2. 2. Navigate to Extensions > Manage > Update
  3. 3. Check for updates to SP Page Builder extension
  4. 4. If an update is available, apply the update to reach version 6.7.1 or later
  5. 5. Alternatively, download SP Page Builder version 6.7.1 or newer from joomshaper.com
  6. 6. Install the updated extension via Extensions > Manage > Install
  7. 7. After installation, verify the version number matches 6.7.1 or higher in the extension manager

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-65877 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-65877 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data