Skip to main content
mySites.guru
CriticalPHP2Shell is fixed, but a researcher now claims six more unpatched PHP flaws. Nothing to do today, but PHP is not out of the woodsWhat to prepare
CVE-2025-54474HighCVSS 8.5CVE published 15 August 2025Added to mySites.guru 20 July 2026

DJ-Classifieds (com_djclassifieds) below 3.11.2 - Unauthenticated Arbitrary File Upload

DJ-Classifieds by DJ-Extensions, all versions before 3.11.2, exposes a front-end file upload endpoint (task=imageupload) that requires no login and validates no CSRF token. An anonymous visitor can write an attacker-named file into the component upload directory, which on a default install is served over the web. Several mitigations were already present in older builds and do reduce the impact: an extension blacklist rejects .php, .phtml, .sh and .js, uploaded content is scanned for patterns such as "<?php", "eval(" and "base64", image extensions are validated with getimagesize(), and temporary files are cleaned up after roughly 12 hours. The content scan only matches the literal "<?php" opening tag, so a short-tag payload ("<?=") survives it, which leaves a polyglot image webshell stored intact and executable on permissive hosts or through a local file inclusion chain. Version 3.11.2 (released 20 July 2026) adds authentication and CSRF/session checks to the imageupload endpoint and enforces a server-side image-only whitelist. Update to 3.11.2 or later. If you cannot update immediately, block POST requests to index.php?option=com_djclassifieds&task=imageupload at the web server or WAF, and check the component upload directory for files you do not recognise. This range also covers the earlier authenticated SQL injection fixed in 3.10.2 (CVE-2025-54474).

Is my site affected?

Affected
DJ-Classifieds before 3.11.2
Fixed in
3.11.2
What to do
Update DJ-Classifieds to 3.11.2 or later.

How CVE-2025-54474 is scored

The base metrics as Joomla CNA published them, and what each one means for a site running an affected version. Threat and environmental metrics are left out: they describe a moment or a particular install rather than the flaw.

8.5 High

CVSS 4.0, scored by Joomla CNA
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

How it is reached

AV:N Attack vector
Network. Reachable across the internet
AC:L Attack complexity
Low. Nothing to work around, it just works
AT:N Attack requirements
None. Works against any affected install
PR:H Privileges required
High. Needs an account with elevated rights
UI:N User interaction
None. Nobody has to be tricked into anything

What it does to the site

VC:H Confidentiality
High. Everything the site holds can be read
VI:H Integrity
High. Data and files can be altered at will
VA:N Availability
None. The site stays up

What it does beyond the site

SC:N Confidentiality
None. Other systems keep their data
SI:N Integrity
None. Other systems keep their integrity
SA:N Availability
None. Other systems stay up

The rule below is rated Critical for the set of 2 CVEs it covers together, not for this record on its own.

Timeline

  1. 15 August 2025CVE-2025-54474 record published by its CNA
  2. 20 July 2026mySites.guru check added for DJ-Classifieds (before 3.11.2)

Rule details

Other vulnerabilities in DJ-Classifieds

Updating for CVE-2025-54474 alone can leave a site on a release another rule still matches. These are the other flaws we check for in the same extension.

DJ-Classifieds

Latest safe version: 3.11.2

References

CVE-2025-54474 questions

Which versions are affected by CVE-2025-54474?
CVE-2025-54474 affects DJ-Classifieds before 3.11.2. The fix is in 3.11.2.
How do I fix CVE-2025-54474?
Update DJ-Classifieds to 3.11.2 or later. Then confirm the installed version on the Joomla administrator's Extensions: Manage screen.
How severe is CVE-2025-54474?
Joomla CNA scores it 8.5 (High) under CVSS 4.0. In plain terms: reachable across the internet, needs an account with elevated rights and nobody has to be tricked into anything.

Running an affected version on a site you manage?

A free audit tells you which of your Joomla and WordPress sites run an affected version, which are out of date, and which have not been backed up. No card required. If a site is already compromised, fix.mysites.guru is a single fixed fee per incident, usually resolved the same day.

This check is part of the mySites.guru Joomla vulnerability scanner, which reads every installed extension's version on each audit. Browse the rest of the Joomla vulnerability database.

Rules current as of 25 October 2026.