dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-57831

HIGH · 8.7 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 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 - digital-peak.com - Unauthenticated blind SQL injection in DP Calendar 8.18.0 - 10.11.2 - The Joomla extension DP Calendar is vulnerable to an unauthenticated SQL injection.

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

The DP Calendar Joomla extension from digital-peak.com versions 8.18.0 through 10.11.2 contains an unauthenticated blind SQL injection vulnerability, allowing remote attackers to inject malicious SQL queries via unspecified input parameters without requiring authentication.

MitigationUpdate DP Calendar to the latest version immediately to patch the SQL injection vulnerability. If patching is not possible, restrict access to the Joomla site or disable the extension until an update can be applied.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/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. Verify DP Calendar extension is installed
    Check Joomla extensions list in the administrator panel under System > Manage > Extensions, or inspect the #__extensions database table for the DP Calendar component
    Affected if The DP Calendar extension (com_dpcalendar) appears in the installed extensions list
  2. Identify installed DP Calendar version
    In Joomla admin, go to Components > DP Calendar > Dashboard to view the version, or query the #__extensions table for the version field where element='dpcalendar'
    Affected if The reported version falls between 8.18.0 and 10.11.2 inclusive
  3. Confirm extension is publicly accessible
    Check if the DP Calendar component is published and not restricted by access levels in the component settings, and verify the Joomla site is publicly reachable
    Affected if The extension is enabled and the site allows unauthenticated access to the component
  4. Review web server and application logs for SQL injection indicators
    Examine access logs for unusual SQL syntax patterns in URL parameters targeting DP Calendar routes (typically index.php?option=com_dpcalendar)
    Affected if Log entries show SQL meta-characters (UNION, SELECT, INSERT, --, #) in query parameters to DP Calendar endpoints that did not originate from your own traffic

The environment is affected if DP Calendar extension is installed with a version between 8.18.0 and 10.11.2 and is accessible to unauthenticated users on the network.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update DP Calendar to the latest version immediately to patch the SQL injection vulnerability. If patching is not possible, restrict access to the Joomla site or disable the extension until an update can be applied.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57831 — 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-57831 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