EFence CVE-2026-80235

The required condition is network reachability of EFence's file upload feature - the attacker must be able to reach the upload endpoint and, for full RCE, the uploaded file must land in a location the web/application server will execute. Per the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N), no authentication, no user interaction, and no special attack requirements are needed against a default-exposed deployment. Limiting factors that reduce real-world exposure: the vulnerability affects only EFence builds from 0 through 1.2.66 (DB Ver:56); instances not exposed to the attacker's network (internal-only or behind a VPN/allowlist) are not remotely reachable; and controls that disable script execution in the upload directory would block the code-execution step even if a file is uploaded.

The signals largely agree on high but not maximally urgent priority. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H) scores 9.3 and describes trivial, unauthenticated, network-reachable exploitation with total impact - consistent with the SSVC assessment of Automatable:yes and Technical Impact:total. However, SSVC records Exploitation:none (no observed exploitation) and there is no CISA KEV listing and no identified public exploit, so this is not confirmed active exploitation. EPSS is moderate at 0.68% (50th percentile), which is unremarkable and reflects the absence of published exploit code rather than any technical barrier. The combination - very low technical bar and total impact, but no evidence of in-the-wild use yet - makes this a strong patch-soon candidate, especially given how readily web-shell upload flaws are weaponized once details circulate. No conflicting signals were observed; the main gap is the lack of an independently confirmed fixed version.

A remote attacker with no account sends a crafted multipart HTTP POST to EFence's file upload endpoint, submitting a web shell disguised as or delivered as an executable server script. Because the application does not validate file type, the shell lands in a web-accessible path; the attacker then requests its URL to execute commands as the web server user, achieving full RCE. No public proof-of-concept is identified at this time, but the network attack vector and low complexity make reliable exploitation straightforward once the endpoint is known.