VULNpocalypse

CVE-2026-12195: myvesta vesta vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

myVesta is affected by an authenticated remote code execution vulnerability. Low privileged users can insert arbitrary commands as a part of the v_ftp_user parameter when deleting FTP usernames. This could result in the execution of commands as the admin user or takevoer of the admin user in myVesta.

Description quoted from the CVE record (assigned by PRJBLK, published 2026-07-04).

Weakness: CWE-78 Improper neutralization of special elements used in an OS command (‘OS command injection’)

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality high, integrity none, availability none. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Also known as: EUVD-2026-41665, GHSA-233w-5rfj-8hmj

VEDAS cluster: VEDAS:CURRENTCROWN

Exploit Observer links 3 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (3)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Vulnerability databases and vendor advisories (3)

Catalogue entries, not exploit evidence.

3 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.007
low predicted chance of attack
VEDAS
0.976
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Suricata

Who is affected

ProductAffectedNot affected
myvesta vestabefore 95d7e43bf286 (git commit)Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Vendor guidance:

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-12195 myVesta Authenticated OS Command Injection via v_ftp_user. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-12195 myVesta Authenticated OS Command Injection via v_ftp_user"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/edit/web/"; nocase; fast_pattern; http.request_body; content:"v_ftp_user"; nocase; pcre:"/v_ftp_user[^&]*(?:\x3b|\x7c|%3b|%7c|\x60|%60|\x24\x28|%24%28|&&|\x0a)/i"; classtype:web-application-attack; reference:cve,CVE-2026-12195; reference:url,https://www.exploit.observer/?keyword=CVE-2026-12195&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=myvesta&match=exact; sid:1096404; rev:1;)

CVE-2026-12195.rules on GitHub

References

Vendor advisories and patches

Exploits and technical analysis

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.