# CVE-2026-57831: Joomla Extension - digital-peak.com - Unauthenticated blind SQL injection in DP Calendar 8.18.0 - 10.11.2

> Unauthenticated attackers can perform blind SQL injection to read database contents in the DP Calendar extension for Joomla.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-r6gc-42q2-64m6

## What is CVE-2026-57831?

CVE-2026-57831 is a high-severity SQL injection vulnerability in digital-peak.com DP Calendar extension for Joomla, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-57831?


## How do I fix CVE-2026-57831?

No fix has been published for CVE-2026-57831 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-57831 being exploited?

There is no known exploitation of CVE-2026-57831 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57831 and fix it if it is affected.

What it is: CVE-2026-57831 is a high-severity SQL injection vulnerability in digital-peak.com DP Calendar extension for Joomla, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57831 in the wild and no public exploit code.

Affected product: digital-peak.com DP Calendar extension for Joomla. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57831/ (Markdown: https://insights.sbomify.com/CVE-2026-57831/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57831
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57831
- OSV: https://osv.dev/vulnerability/CVE-2026-57831

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57831/
Summaries are generated and may contain mistakes; the official description above is the record.