dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-49467

CRITICAL · 9.3 CVSS v4.0 Published 2025-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 JEvents component before 3.6.88 and 3.6.82.1 for Joomla was discovered. The extension is vulnerable to SQL injection via publicly accessible actions to list events by date ranges.

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 JEvents Joomla component allows attackers to inject malicious SQL queries through publicly accessible date range event listing actions, potentially enabling data exfiltration or database compromise.

MitigationUpdate JEvents component to version 3.6.88 or 3.6.82.1 or later to apply the security patch.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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:Y/R:X/V:X/RE:X/U:Amber

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 JEvents component is installed
    Check for the JEvents component in the Joomla administrator panel under Components > JEvents, or look for the com_jevents directory in the /components/ folder on the file system
    Affected if JEvents component is present in the Joomla installation
  2. Identify installed JEvents version
    Access the JEvents component in the Joomla admin panel and navigate to the About or Components > JEvents page to view the version number, or check the manifest XML file in the com_jevents directory
    Affected if The displayed version is earlier than 3.6.88 or 3.6.82.1 (if 3.6.x series) or below 3.6.82.1 for the 3.6.x branch
  3. Verify date range event listing is enabled
    In the Joomla admin, go to Components > JEvents > Configuration or Parameters and check if the date range event listing functionality is enabled. This feature is typically found in the component settings under event display options
    Affected if Date range event listing is enabled in the JEvents configuration
  4. Check if date range listing is publicly accessible
    Examine the menu item configuration for JEvents in the Joomla menu manager. Look for menu items of type JEvents > Event List or similar that may expose date range parameters. Verify if these menu items are published and assigned to a public-access menu
    Affected if Menu items exposing date range event listing are published to a public-access menu or no menu item access restrictions are configured for date range features
  5. Compare version against vulnerable range
    Document the exact version number found and compare it against the affected versions: any version below 3.6.88 or 3.6.82.1 in the 3.6.x branch is vulnerable
    Affected if Installed version is below 3.6.88 and also below 3.6.82.1, placing it within the vulnerable range

The environment is affected if JEvents is installed with a version earlier than 3.6.88 or 3.6.82.1 AND the date range event listing feature is enabled and publicly accessible.

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 JEvents component to version 3.6.88 or 3.6.82.1 or later to apply the security patch.

Recommended fix Moderate confidence

JEvents 3.6.88 or later (or 3.6.82.1 for the 3.6.82 branch)

  1. 1. Backup your Joomla site and database before making any changes
  2. 2. Navigate to the JEvents component in your Joomla administrator panel
  3. 3. Check your current JEvents version in the component's about/info section
  4. 4. Download the latest JEvents version from the official source at jevents.net
  5. 5. Install the update through Joomla's extension manager: Extensions > Manage > Install
  6. 6. Verify the installed version is 3.6.88 or later
  7. 7. Test that the event listing functionality works correctly
  8. 8. Clear any caching if applicable
Caveat Review JEvents changelog for any template/override changes that may affect customizations

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-2025-49467 — 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-49467 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