Skip to main content
VulnerabilityPublished

CVE-2025-50127: dj-extensions.com DJ-Flyer component for Joomla · SQL Injection

Affects dj-extensions.com DJ-Flyer component for JoomlaSource CVE Database V5

0

Not known to be exploited · CVSS 8.5 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jul 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
dj-extensions.com DJ-Flyer component for JoomlaAffected
  • =1.0-3.2
Fixed in–

AI-suggested

  1. Immediate mitigation should include restricting access to the DJ-Flyer component to only trusted and essential privileged users to reduce the attack surface.
  2. Implement web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the DJ-Flyer endpoints.
  3. Conduct thorough code reviews and input validation enhancements in the DJ-Flyer component to ensure proper sanitization and parameterization of all SQL queries.
  4. Monitor logs for unusual database queries or access patterns indicative of SQL injection attempts.
  5. Isolate Joomla instances running vulnerable DJ-Flyer versions in segmented network zones to limit potential lateral movement.
  6. Engage with the vendor or community to obtain or develop patches and apply them promptly once available.
  7. Educate privileged users on the risks of SQL injection and enforce strong authentication and session management practices to prevent credential compromise.
  8. Regularly back up databases and test restoration procedures to minimize downtime and data loss in case of exploitation.

Description

A SQLi vulnerability in DJ-Flyer component 1.0-3.2 for Joomla was discovered. The issue allows privileged users to execute arbitrary SQL commands.

References

Community reviews

Loading reviews…