AcymailingApplication
CVE-2023-39974
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 · uneditedExposure of Sensitive Information vulnerability in AcyMailing Enterprise component for Joomla. It allows unauthorized actors to get the number of subscribers in a specific list.
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 confidenceAn information disclosure vulnerability in AcyMailing Enterprise for Joomla allows unauthenticated or unauthorized attackers to query an API endpoint and retrieve the subscriber count for any mailing list without proper authentication or authorization checks.
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
>= 6.7.0, < 8.7.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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify AcyMailing installed versionCheck the AcyMailing version in Joomla admin under Components > AcyMailing > Dashboard, or query the #__extensions table in the database where name LIKE '%acymailing%'Affected if Version is >= 6.7.0 and < 8.7.0
-
Locate the subscriber count API endpointExamine AcyMailing routing configuration or component files to identify the endpoint path for retrieving mailing list subscriber counts - typically under the stats or list controllerAffected if The endpoint exists and is accessible via the web
-
Verify API endpoint is unauthenticatedAttempt an HTTP request to the subscriber count endpoint without providing any authentication tokens or credentialsAffected if The endpoint returns subscriber count data without requiring authentication
-
Check for list ID parameter exposureTest the endpoint with different list ID values to confirm arbitrary mailing list subscriber counts can be retrievedAffected if Different list IDs return corresponding subscriber counts without authorization checks
-
Review API access controls in configurationIn AcyMailing configuration under API or Access settings, verify whether subscriber count endpoints have authentication enforcedAffected if No authentication or authorization is required for subscriber count queries
The environment is affected if AcyMailing version is between 6.7.0 and 8.7.0 and the subscriber count API endpoint is accessible without authentication.
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 · scoped8.7.0
Implement proper authentication and authorization checks on the mailing list subscriber count endpoint to ensure only authorized users can access subscriber data.
8.7.0
- 1. Back up your Joomla site and AcyMailing database before proceeding
- 2. Download AcyMailing version 8.7.0 from the official AcyMailing website (www.acymailing.com) or Joomla Extensions Directory (extensions.joomla.org)
- 3. Install the update through Joomla's Extension Manager using the 'Update' function or by uploading the new package
- 4. Clear any Joomla and AcyMailing caches after the upgrade
- 5. Verify that the vulnerability is resolved by confirming unauthorized users can no longer access subscriber counts
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Acymailing
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39974 — 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-39974 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