Skip to main content
CVE-2025-49467VulnerabilityPublished

CVE-2025-49467: JEvents component for Joomla · SQL Injection

Affects JEvents component for JoomlaSource CVE Database V5

0

Not known to be exploited · CVSS 9.3 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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/AU:Y/U:Amber

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
jevents.net / GWE Systems Ltd JEvents component for JoomlaAffected
  • =1.0.0-3.6.82
  • =3.6.83-3.6.87
Fixed in–

AI-suggested

1. Immediate upgrade: Organizations should promptly update the JEvents component to version 3.6.88 or later, where this vulnerability is patched. 2. Input validation and sanitization: Until patching is possible, implement web application firewall (WAF) rules to detect and block suspicious SQL injection patterns targeting the event listing endpoints. 3. Restrict access: If feasible, restrict access to the vulnerable endpoints by IP whitelisting or requiring authentication to reduce exposure. 4. Database permissions: Ensure the database user account used by Joomla has the minimum necessary privileges, limiting the potential damage from SQL injection. 5. Monitoring and logging: Enable detailed logging of web requests and database queries to detect anomalous activities indicative of exploitation attempts. 6. Incident response readiness: Prepare to respond to potential data breaches, including backups verification and forensic analysis capabilities. 7. Code review: For organizations with custom Joomla extensions or modifications, review code for similar SQL injection risks and apply secure coding practices. These targeted measures go beyond generic advice by focusing on immediate containment, access control, and proactive detection tailored to the JEvents component's specific vulnerability.

Description

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.

References

Community reviews

Loading reviews…