Acymailing StarterApplication · Acyba
CVE-2023-39970
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in AcyMailing component for Joomla. It allows remote code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an unrestricted file upload vulnerability in the AcyMailing component for Joomla. The component fails to properly validate uploaded file types, allowing attackers to upload dangerous files (likely PHP scripts) that can be executed for remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Acymailing StarterApplication
>= 6.7.0, <= 8.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed AcyMailing versionNavigate to Joomla admin > Components > AcyMailing, or check the version listed in Joomla's extension manager under the AcyMailing component entryAffected if The version displayed is greater than or equal to 6.7.0 and less than or equal to 8.5.0
-
Confirm file upload is enabled in AcyMailingIn the Joomla admin panel, go to AcyMailing > Configuration > Security settings, or check if the file upload functionality is accessible in the component's list or import featuresAffected if File upload or import functionality is enabled and accessible to users
-
Check component access permissionsNavigate to Joomla > Components > AcyMailing > Users > Access Levels, or check the ACL settings to determine which user groups can access file upload featuresAffected if User groups with access to file upload have permission to upload files through the component
Your environment is affected if AcyMailing Starter version 6.7.0 through 8.5.0 is installed AND the file upload feature is enabled for any user group with access to the component.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade AcyMailing to the latest patched version. If immediate patching is not possible, disable the file upload functionality or restrict access to the component via firewall/ACL until the patch can be applied.
Acymailing Starter version > 8.5.0 (latest stable release)
- 1. Navigate to the Acymailing component in your Joomla administrator panel.
- 2. Verify your current Acymailing version is between 6.7.0 and 8.5.0 (inclusive) to confirm vulnerability.
- 3. Before upgrading, backup your Joomla database and files.
- 4. Download the latest Acymailing Starter version from the official Joomla Extensions Directory or Acymailing website.
- 5. Install the update through Joomla's extension manager.
- 6. Verify the new version is installed and the vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Acymailing Starter
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39970 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-39970 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data