dbcve.org
AcymailingApplication

CVE-2023-28732

HIGH · 7.5 CVSS v3.1 Published 2023-03-30
Fix available
A fix is available. Upgrade to 8.3.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Missing access control in AnyMailing Joomla Plugin allows to list and access files containing sensitive information from the plugin itself and access to system files via path traversal, when being granted access to the campaign's creation on front-office. This issue affects AnyMailing Joomla Plugin in versions below 8.3.0.

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 · high confidence

Missing access control combined with path traversal vulnerability in the AnyMailing Joomla plugin allows authenticated users with front-office campaign creation privileges to read sensitive plugin files and traverse the file system to access system files outside the web root.

MitigationUpgrade AnyMailing Joomla Plugin to version 8.3.0 or later, which implements proper access controls and path validation to prevent unauthorized file access.

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
AcymailingApplication
Affected:< 8.3.0

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Acymailing plugin is installed
    Check the Joomla administrator extensions manager for the Acymailing component and AnyMailing plugin, or look for Acymailing-related directories in the Joomla installation.
    Affected if Acymailing or AnyMailing extension is present in the Joomla installation
  2. Determine the installed Acymailing version
    Access the Joomla administrator panel, navigate to Components > Acymailing, and check the version displayed in the component's about or configuration page. Alternatively, check the manifest XML file in the Acymailing plugin directory.
    Affected if The installed version is lower than 8.3.0 (e.g., 8.2.x, 8.1.x, or earlier)
  3. Check if front-office campaign creation is enabled
    In Joomla admin, go to Acymailing configuration > Access Rights or User Permmissions settings. Verify whether permission for front-office users to create campaigns is granted to any user group.
    Affected if Authenticated users have front-office campaign creation privileges enabled in Acymailing access settings
  4. Inspect plugin file permissions and configuration
    Review the AnyMailing plugin configuration files in the Joomla administrator for any file read or import functionality that lacks proper authorization checks.
    Affected if The AnyMailing plugin configuration shows file read/import features accessible to authenticated front-office users without role validation

Your environment is affected if Acymailing AnyMailing plugin version is below 8.3.0 and authenticated front-office users have campaign creation privileges enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.3.0 or later
Fixed in 8.3.0
Interim mitigation

Upgrade AnyMailing Joomla Plugin to version 8.3.0 or later, which implements proper access controls and path validation to prevent unauthorized file access.

Recommended fix High confidence

8.3.0 or later

  1. 1. Create a complete backup of your Joomla database and Acymailing installation before updating
  2. 2. Download Acymailing version 8.3.0 or later from the official source at www.acymailing.com
  3. 3. Navigate to your Joomla administration panel and access the Extensions > Manage section
  4. 4. Upload and install the Acymailing 8.3.0+ update package
  5. 5. Clear any Joomla and browser caches after the update
  6. 6. Verify the installation was successful by checking the Acymailing version in Components > Acymailing
  7. 7. Test that users with front-office campaign creation access can no longer perform path traversal attacks
  8. 8. Confirm all Acymailing functionality (sending, list management, templates) operates normally
Caveat none

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Acymailing Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28732 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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