dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-49468

HIGH · 8.6 CVSS v4.0 Published 2025-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
A SQL injection vulnerability in No Boss Calendar component before 5.0.7 for Joomla was discovered. The vulnerability allows remote authenticated users to execute arbitrary SQL commands via the id_module parameter.

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

SQL injection vulnerability in the No Boss Calendar Joomla component allows authenticated attackers to inject arbitrary SQL commands through the id_module parameter, potentially exposing or manipulating the database.

MitigationUpdate No Boss Calendar component to version 5.0.7 or later to patch the SQL injection vulnerability. Additionally, apply least-privilege principles to database accounts used by the component.

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:H/VA:H/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. Locate No Boss Calendar component installation
    Inspect Joomla's component directory for com_nobosscalendar folder. Common paths: /administrator/components/com_nobosscalendar/ or /components/com_nobosscalendar/
    Affected if The component directory exists in the Joomla installation
  2. Determine installed version of No Boss Calendar
    Check the component's manifest XML file (e.g., admin/nobosscalendar.xml) or a dedicated version file within the component directory for the <version> tag
    Affected if The installed version is identified as lower than 5.0.7
  3. Verify authenticated user access to the component
    Check Joomla's #__assets or #__extensions table, or inspect the component's access permissions in Joomla administrator under Components > No Boss Calendar > Permissions
    Affected if Authenticated users (with any privilege level) have access to the component's functionality
  4. Confirm id_module parameter usage in component
    Review component source files (controllers, models, views) for usage of the 'id_module' request parameter in database queries, particularly in files like controller.php, model.php, or view.html.php within the component
    Affected if The id_module parameter is used in SQL queries without proper sanitization/prepared statements

The environment is affected if No Boss Calendar is installed with a version lower than 5.0.7 and authenticated users can access the component's functionality that utilizes the id_module parameter in database operations.

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

Update No Boss Calendar component to version 5.0.7 or later to patch the SQL injection vulnerability. Additionally, apply least-privilege principles to database accounts used by the component.

Recommended fix High confidence

No Boss Calendar 5.0.7 for Joomla

  1. 1. Log in to the Joomla administrator panel
  2. 2. Navigate to Extensions > Manage to check the currently installed version of No Boss Calendar
  3. 3. If the installed version is below 5.0.7, back up the Joomla site and database
  4. 4. Download No Boss Calendar version 5.0.7 or later from the official vendor (nobossextensions.com)
  5. 5. Install the updated component via Extensions > Manage > Install
  6. 6. Verify the new version is installed correctly
  7. 7. Confirm the SQL injection vulnerability is remediated by testing the id_module parameter

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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