CVE-2025-26855
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 · uneditedA SQL injection in Articles Calendar extension 1.0.0 - 1.0.1.0007 for Joomla allows attackers to execute arbitrary SQL commands.
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 · moderate confidenceA SQL injection vulnerability exists in the Articles Calendar extension for Joomla versions 1.0.0 through 1.1.0007. The vulnerability allows remote attackers to inject malicious SQL statements through unsanitized input parameters, potentially enabling unauthorized database access, data exfiltration, or manipulation of application data.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Articles Calendar extension is installedLog into the Joomla administrator panel and navigate to Extensions > Manage, or query the #__extensions table in the Joomla database to confirm the Articles Calendar extension is present.Affected if The extension is not installed, the vulnerability does not apply.
-
Identify the installed version numberIn the Joomla administrator panel under Extensions > Manage, locate the Articles Calendar extension and note the version column, or query the version field from the #__extensions table where name LIKE '%Articles Calendar%'.Affected if The exact installed version cannot be determined from the extension metadata.
-
Compare version against affected rangeReview the identified version against the vulnerable range 1.0.0 through 1.1.0007. Versions 1.0.0, 1.0.x, 1.1.0, and up to and including 1.1.0007 are affected.Affected if The installed version falls within 1.0.0 to 1.1.0007, indicating the vulnerability exists in this deployment.
-
Confirm the calendar component is accessibleVerify the Articles Calendar component is published and accessible on the frontend via its menu item or direct URL (typically index.php?option=com_articlescalendar or similar component route).Affected if The component is not published or accessible, the attack surface may be reduced but the vulnerable code still exists.
The environment is affected if the Articles Calendar extension is installed and its version falls within 1.0.0 to 1.1.0007, as the SQL injection vulnerability is present in all versions within this range.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of the Articles Calendar extension that implements proper input validation and uses parameterized queries/prepared statements for all database operations. If no patched version is available, disable the extension until a fix is released.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26855 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26855 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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