Skip to main content
Menu
CVEs

Visforms extension for Joomla remote code execution via CSS editor

CVE-2026-129396EUVD-2026-130471Published November 19, 2026, updated

9.4CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 5.6.4
Who is exposed
Specific setups only

Summary

The Visforms extension for Joomla from vi-solutions has a flaw in its CSS editor that lets a privileged backend user write arbitrary PHP files, which can lead to remote code execution. The attack can be carried out remotely over the network, but it requires an attacker with high-level login privileges.

Written by a model

Original description

Joomla Extension - vi-solutions - Arbitrary file write leading to remote code execution in CSS editor in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The CSS editor did not restrict file names, extensions and paths of created and saved files, allowing privileged backend users to write arbitrary PHP files.

What to do

Upgrade to a fixed version: 5.6.4.

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-129396 (Joomla Extension - vi-solutions - Arbitrary file write leading to remote code execution in CSS editor in Visforms extension 1.0.0-5.6.3…), 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-129396 (entry last updated 2026-11-19):
Affected:
- vi-solutions Visforms extension for Joomla: versions 1.0.0-5.6.3, 6.0.0-6.2.0
Fixed versions: 5.6.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-129396 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129396 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://vi-solutions.de/en/joomla-form-extension-visforms
- https://docs.joomla-6.visforms.vi-solutions.de/en/updates/j6/version-6-2-x/
- https://docs.joomla-6.visforms.vi-solutions.de/en/updates/j5/version-5-6-x/
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-129396
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-129396"}.

Affected versions

cve.now Index

18Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.4, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  5. Record last updated

Evidence 5

Questions about CVE-2026-129396

Is CVE-2026-129396 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-129396?

Visforms extension for Joomla: versions 1.0.0-5.6.3, 6.0.0-6.2.0.

Source: cve.now feed data

How do I fix CVE-2026-129396?

Upgrade the Visforms extension to version 5.6.4, the fixed release listed in the vendor's advisory dated August 18, 2026.

Source: docs.joomla-6.visforms.vi-solutions.de

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