Joomla: SSRF (server-side request forgery)
Joomla
SSRF (server-side request forgery) in the Joomla component. Threat level: High (CVSS 8.5).
Who is affected
This vulnerability affects: Joomla. If you use this component on your site, check the version and update it as soon as possible.
How dangerous
Rating: High, CVSS 8.5 out of 10. It is worth acting before the flaw is exploited.
What this flaw is
SSRF forces the site server to send a request on the attacker's behalf, e.g. to internal network resources normally unreachable from the outside.
It is used to map infrastructure and reach data that was meant to be hidden from the internet.
Score breakdown (CVSS vector)
What the CVSS 8.5 rating means in practice:
- The attack can be carried out remotely, over the internet.
- Requires an account with elevated privileges.
- Requires no action from the victim.
Weakness class: CWE-918.
How to fix: SSRF (server-side request forgery)
- Update the component that permits the server-side request.
- Restrict the server's outbound connections and block access to internal/metadata addresses.
- Review logs for unexpected outbound requests originating from the server.
Prefer not to do this yourself? We will handle the update, check for signs of a break-in and secure the site. Write to us →
Frequently asked questions
Does this vulnerability affect my site?
It affects sites that use Joomla. Check whether you have this component installed and which version, the flaw only applies to the vulnerable version range. You can verify it in under a minute with our free vulnerability scanner.
How do I check whether I have the vulnerable version?
In your admin panel (in WordPress: Plugins / Themes) check the installed version of Joomla and compare it with the vendor advisory that names the fixed version. If it is lower, or you are not sure, run our scanner, which reads the versions visible in the site code.
How urgently should I react?
This is a Wysoka-severity flaw, so treat it as urgent, high-impact vulnerabilities are often exploited automatically within hours of disclosure. Update as soon as possible.
What if a patch is not available yet?
Until a fix ships, reduce the exposure: temporarily disable the vulnerable component, restrict access to the affected functionality, or add a WAF rule blocking the vulnerable request. Keep a current off-site backup and watch for signs of a break-in.
Is updating alone enough?
If the site has not been attacked yet, updating to the patched version closes the hole. If there are already signs of compromise (unknown files, new admin accounts, redirects), the update does not undo the break-in, you also need to clean the site and rotate passwords and the WordPress salts.
Does this flaw affect your site?
We will run a free audit: we check versions, plugins, and configuration, and tell you plainly whether you are safe.
Request a free audit →