Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach public AcyMailing subscription form
-
DeliveryStore traversal path in file-type custom field
-
ExploitClear field to trigger cleanup deletion
-
ExecutionAcyMailing deletes path outside upload folder
-
Impactconfiguration.php removed, site broken
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitable when an AcyMailing Enterprise instance older than 11.1.0 exposes a subscription or profile form containing a file-type custom field that is publicly reachable (no authentication, per PR:N). The attacker stores an arbitrary path (including traversal outside the upload folder) in that field and then clears the field, which is what triggers AcyMailing's file-deletion routine on the attacker-supplied path. Limiting factors: a file-type custom field must actually be configured and web-accessible, and the deletion fires on the field-clear workflow (reflected as AT:P) rather than on any arbitrary request - so a default install without such a custom field is not exploitable. Impact is destructive (file deletion, e.g. configuration.php) rather than data theft. |
| Impact | This is a genuinely serious flaw whose severity is well-supported by the CVSS 4.0 vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H: remote, network-reachable, low complexity, no privileges and no user interaction, delivering high integrity and availability impact. The AT:P (attack requirement 'present') modifier reflects the one non-trivial precondition - the vulnerable file-type custom field must exist on a public subscription form and the deletion is triggered when the field is cleared - which is why the score lands at 8.3 rather than near 9.5. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no evidence of active exploitation or automated weaponization; risk is currently theoretical-but-high-plausibility given how mechanically simple the attack is. One clear data conflict: the CWE is CWE-89 (SQL Injection) and a 'SQLi' tag is present, but the description unambiguously describes arbitrary file deletion via attacker-controlled paths (a path-traversal / external-control-of-filename class issue, CWE-22/CWE-73), not SQL injection - the classification should be treated as wrong. Net: a real priority for exposed Joomla sites running AcyMailing subscription forms, but not a confirmed in-the-wild emergency. |
| Exploit ScenarioDerived | An attacker visits a public AcyMailing subscription or profile-edit form that includes a file-type custom field, submits a crafted value pointing at an application file such as ../configuration.php, then clears the field so AcyMailing performs its cleanup deletion on the attacker-controlled path. The referenced file is removed from disk outside the intended upload directory, breaking the Joomla site. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 26, 2026
Unauthenticated arbitrary file deletion in the AcyMailing Enterprise extension for Joomla (versions before 11.1.0) allows a remote attacker to store an arbitrary filesystem path - including paths that traverse outside the configured upload directory, such as configuration.php - in a file-type custom field and have the extension delete that file when the field is subsequently cleared. Exploitation requires a publicly reachable subscription or profile form that has a file-type custom field configured, so a default installation without such a field is not affected; the CVSS 4.0 vector (CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H) confirms network reachability, low complexity, no privileges required and no user interaction, with high integrity and availability impact but no confidentiality impact, reflecting a purely destructive outcome rather than data theft. No public exploit code and no confirmed active exploitation were identified at time of analysis; the vendor has released a fixed version.
RemediationAI
Upgrade AcyMailing Enterprise for Joomla to 11.1.0 or later, which is the vendor-released fix (the affected range is '< 11.1.0'); consult https://www.acymailing.com/ for the official package and any edition-specific notes, and verify the installed extension version in Joomla's extension manager after updating. Before or where patching is delayed, the highest-value compensating control is to remove or disable any file-type custom fields referenced by publicly reachable subscription or profile forms, or to make those forms non-public - the trade-off is loss of that upload/enrolment functionality, but it eliminates the deletion trigger entirely because the flaw fires only on the field-clear workflow. Restricting the web server user's write access to sensitive files, in particular ensuring configuration.php and the Joomla root are not writable by the PHP process, is a complementary mitigation whose cost is that legitimate Joomla configuration edits and some extension updates must then be performed with elevated filesystem permissions. Maintain offline, readily restorable backups of configuration.php and the site tree so that a successful deletion is a recovery event rather than an outage, and monitor for unexpected disappearance of configuration files or mass file-removal activity as a detection signal. No public exploit code was identified at time of analysis, but the primitive is simple enough that unauthenticated scanning should be assumed plausible, making prompt upgrade the priority.
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
AcyMailing is a widely deployed newsletter and subscription extension for the Joomla CMS, distributed in Community and Enterprise editions. The flaw lives in its custom-field handling: Joomla's custom fields subsystem supports a 'file'-type field whose value is persisted as a stored path and whose cleanup routine deletes the referenced file when the field is emptied or its value is replaced. Because AcyMailing does not canonicalise or confine that stored path to the extension's own upload directory before unlinking it, an attacker who can submit the public subscription/profile form can plant a traversal path (for example ../../configuration.php) in the field and then trigger the deletion by clearing it. The result is an arbitrary file-deletion primitive against files writable by the web server user - classically Joomla's configuration.php, which holds database credentials and the secret token, the removal of which can both take the site offline and expose reusable secrets via error output or degraded handling. Note a metadata inconsistency in the source data: the record is tagged CWE-89 (SQL Injection) and carried in a SQLi-tagged feed, but the actual behaviour described and independently assessed is file deletion driven by unvalidated path handling, which maps more accurately to CWE-22 (Path Traversal) or CWE-73 (External Control of File Name or Path). The CPE string cpe:2.3:a:acymailing.com:acymailing_extension_for_joomla:*:*:*:*:*:*:*:* is version-agnostic, so version scoping must come from the advisory ('< 11.1.0') rather than from CPE matching. The CVSS 4.0 'AT:P' (Attack Requirements: Present) metric properly encodes the precondition that a file-type custom field must exist and be exposed, and that deletion fires on the field-clear workflow rather than on any arbitrary request.
Know when PHP 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:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
Network, low-complexity, unauthenticated deletion of arbitrary files (I:H) that can remove configuration.php and take down the site (A:H); no confidentiality impact and same security scope.
Primary rating from Vendor (Joomla).
CVSS VectorVendor: Joomla
DescriptionCVE.org
Joomla Extension - acymailing.com - Unauthenticated arbitrary file deletion in AcyMailing Enterprise extension < 11.1.0 - A subscriber could store a path in a file-type custom field and have AcyMailing delete that file when the field was cleared, including files outside the upload folder such as configuration.php.
Executive ViewAI
Organizations running the AcyMailing Enterprise extension for Joomla on versions before 11.1.0 are exposed to a destructive, unauthenticated attack path: anyone able to reach a subscription or profile form configured with a file-type custom field can cause the site to delete files of the attacker's choosing, including core configuration files. The outcome is customer-facing website outage and loss of site integrity rather than data theft, which places the risk squarely in business continuity and brand-trust territory. No public exploit code and no confirmed active exploitation were identified at time of analysis, so leadership has a window to remediate proactively.
Apply vendor patch (AcyMailing Enterprise 11.1.0). Where immediate patching is not possible, unpublish or disable publicly reachable subscription and profile forms that contain a file-type custom field, restrict access to those forms, and harden filesystem permissions so the web server user cannot delete configuration.php or other critical files.
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
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
EUVD-2026-87773
GHSA-657v-94xx-8q7f
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB