Skip to main content
Menu
CVEs

FILEman extension for Joomla unauthenticated SSRF in frontend file view

CVE-2026-129422Published November 19, 2026, updated

6.9MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Summary

The FILEman extension for Joomla from joomlatools.com has a blind server-side request forgery flaw in its frontend file view, which does not restrict requested files to their container. Remotely, without logging in, an unauthenticated attacker can make the server send requests to arbitrary addresses, including internal network resources.

Written by a model

Original description

Joomla Extension - joomlatools.com - Unauthenticated blind server-side request forgery in FILEman extension < 6.1.4 - The frontend file view did not restrict requested files to their container and passed URLs to the framework URL fetch, allowing unauthenticated attackers to make the server issue requests to arbitrary addresses, including internal network resources.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129422 (Joomla Extension - joomlatools.com - Unauthenticated blind server-side request forgery in FILEman extension < 6.1.4), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129422 (entry last updated 2026-11-19):
Affected:
- joomlatools.com FILEman extension for Joomla: versions 1.0.0-6.1.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129422 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129422 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.joomlatools.com/extensions/fileman/changelog/6.1.4
- https://www.joomlatools.com/extensions/fileman/
- https://mysites.guru/blog/joomlatools-docman-fileman-security-release/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129422
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129422"}.

Affected versions

cve.now Index

32Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 5

KindSource
Vendor advisory 2Establishes: Affected and fixed versions.
Advisoryjoomlatools.com · extensions/fileman/changelog/6.1.4
Linkjoomlatools.com · extensions/fileman
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129422
RecordNVD · CVE-2026-129422
Other links 1
Linkmysites.guru · blog/joomlatools-docman-fileman-security-release

Questions about CVE-2026-129422

Is CVE-2026-129422 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-129422?

FILEman extension for Joomla: version 1.0.0-6.1.3.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.