Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to ArmorX Spam console
-
ExploitCraft parameter with path-traversal sequence
-
ExecutionTrigger PHP include outside intended directory
-
ImpactDisclose or execute included file contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V5 - File Handling File inclusion prevention, allowlisting
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Command and Control The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid authenticated session on the ArmorX Spam web application (PR:L confirmed in the CVSS vector) - it is not usable by fully unauthenticated attackers. Given that prerequisite, the attacker then supplies path-traversal input to a parameter that the application passes to a PHP include/require (CWE-98), causing inclusion of PHP files outside the intended directory. Limiting factors: the low-privilege credential requirement and the need to reach a specific include-handling endpoint; no user interaction is required (UI:N) and no special non-default configuration is named in the advisory, so default deployments with any valid account appear affected. The exact affected versions are not specified in the provided data. |
| Impact | The input CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H) describes a network-reachable, low-complexity attack that requires low-privilege authentication (PR:L) and yields high confidentiality impact with no integrity or availability impact. There is no EPSS score, no CISA KEV listing, and no public POC referenced in the provided data, so this is 'no public exploit identified at time of analysis' - exploitation is not confirmed active. The authentication requirement (PR:L, confirmed by the vector) is the primary mitigating factor: an attacker must first obtain valid credentials on the ArmorX Spam console, which meaningfully reduces exposure to opportunistic mass exploitation. Note a conflict worth flagging: the vendor-assigned vector scopes impact as confidentiality-only (VC:H/VI:N/VA:N), yet the description and CWE-98 (improper control of filename for PHP include) imply the application includes PHP files, which commonly enables code execution rather than mere file disclosure - this suggests the integrity/availability impact may be understated and should be verified with the vendor. Overall this is a moderate, authenticated-only priority rather than an internet-wide emergency, given the credential prerequisite, absence of exploitation evidence, and a regional/niche product footprint. |
| Exploit ScenarioDerived | An attacker who already holds a low-privilege authenticated session on the ArmorX Spam web interface submits a request containing path-traversal sequences in a parameter that feeds a PHP include/require call, causing the application to load a PHP file from outside the intended directory. No public exploit code is identified, but CWE-98 LFI with PHP inclusion is a well-understood class, and the low attack complexity (AC:L) means exploitation is straightforward once credentials are obtained. Depending on what files are reachable, this can disclose sensitive application/configuration data or, if attacker-controllable PHP can be reached, lead to code execution. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 20, 2026
Local file inclusion in ArmorX Spam allows remote attackers with a valid low-privilege authenticated session to traverse directories and cause PHP include/require statements to load files outside the intended path, exposing sensitive local data. The issue is network-reachable and low-complexity but requires authentication (PR:L); no public exploit identified at time of analysis, and no CISA KEV entry is present. The assessed impact is high confidentiality loss only, with no integrity or availability impact.
RemediationAI
No vendor-released patch version is identified in the provided data, so the primary action is to obtain and apply the ArmorX Global Technology update for ArmorX Spam when released and verify remediation status through the TWCERT advisories at https://www.twcert.org.tw/tw/cp-132-11294-4e5d8-1.html and https://www.twcert.org.tw/en/cp-139-11295-f2efd-2.html. As compensating controls, restrict access to the affected include-handling endpoints to trusted authenticated users and minimize low-privilege account exposure; this reduces attack surface but does not correct the flaw and may limit legitimate access. Replace user-controlled include paths with a fixed allowlist of permitted filenames and canonicalize with realpath(), rejecting any resolved path outside the application base directory; this is effective but may break legitimate dynamic include behavior and requires application changes. Disable allow_url_include and unnecessary PHP stream wrappers, reject traversal sequences after normalization and URL-decoding, and monitor web logs for ../ and encoded traversal patterns as a detection control; these measures reduce exploitability and improve visibility but are not substitutes for a vendor fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-98, improper control of a filename used in a PHP include/require statement. PHP include and require constructs accept file paths supplied by the application; when user-controlled input reaches such a statement without canonicalization and allowlisting, path-traversal sequences can escape the intended directory and cause local files to be included. This case is a local file inclusion manifestation rather than remote file inclusion. The affected CPE is cpe:2.3:a:armorx_global_technology:armorx_spam:*:*:*:*:*:*:*:*, with the wildcard indicating that no specific vulnerable version range is enumerated in the provided data. The independent CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N confirms network reachability, low attack complexity, low-privilege authentication, no user interaction, and high confidentiality-only impact; the original CVSS 4.0 vector is consistent in requiring PR:L and showing VC:H with VI:N and VA:N. The advisory does not name a non-default configuration prerequisite, so default deployments with any valid account appear affected, though reaching the specific include-handling endpoint is required.
Know when Armorx Spam gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable PHP LFI requiring a low-privilege account (PR:L, AV:N, AC:L, UI:N); scored confidentiality-only (C:H) per vendor impact, though CWE-98 may warrant higher integrity impact.
Primary rating from Vendor (twcert).
CVSS VectorVendor: twcert
DescriptionCVE.org
ArmorX Spam developed by ArmorX Global Technology has a Local File Inclusion vulnerability. Authenticated remote attackers can exploit path traversal to cause the application to include PHP files outside the intended directory.
Articles & Coverage 1
Executive ViewAI
ArmorX Spam contains a high-severity local file inclusion weakness that lets anyone holding even a basic authenticated account pull files from outside the application's intended directory - potentially exposing configuration secrets, stored credentials, or customer records held on the same server. Because the barrier is a low-privilege login rather than administrative access, the realistic exposure set extends to contractors, shared service accounts, and any end-user credential that has been phished or reused, not just trusted administrators. Leadership should note that the vendor has not yet shipped a fix, so residual risk on this system will persist until a patch is released and deployed.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict network access to ArmorX Spam instances (VPN or IP allowlisting), remove or disable unnecessary low-privilege accounts and enforce least privilege, deploy WAF/reverse-proxy rules blocking path traversal sequences in request parameters, enable file integrity monitoring and alerting on unexpected file reads, and review web/application logs for traversal attempts while awaiting the vendor fix.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Local File Inclusion vulnerabilities occur when an application accepts user-controlled input to specify which file should be loaded or executed, typically through functions like PHP's `include()`, `require()`, or `fopen()`.
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
EUVD-2026-104809
GHSA-4v9g-qvqj-2jr7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB