dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-57740

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click 5 weeks old

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 Authorization vulnerability in AcyMailing Newsletter Team AcyMailing SMTP Newsletter acymailing allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects AcyMailing SMTP Newsletter: from n/a through <= 10.11.1.

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 confidence

AcyMailing SMTP Newsletter versions up to 10.11.1 contain a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. The vulnerability stems from insufficient access control checks on certain functionality, potentially enabling unauthenticated or unauthorized users to access sensitive operations.

MitigationImplement proper authorization checks on all sensitive endpoints and functions within AcyMailing, ensuring that access is restricted based on user roles and permissions. Review and enforce the principle of least privilege across the application's access control configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 checks

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

  1. Identify AcyMailing version installed
    Access the Joomla administrator panel, navigate to Components > AcyMailing, and locate the version number typically displayed on the main dashboard or in the component information page. Alternatively, check the manifest file (xml) in the /administrator/components/com_acymailing/ directory for the version tag.
    Affected if The installed version is 10.11.1 or any version below it (e.g., 10.10.x, 10.9.x, earlier versions), since the vulnerability affects versions up to and including 10.11.1.
  2. Verify access control configuration
    In the AcyMailing component under Joomla admin, navigate to Configuration > Access Control or Security Settings. Examine the security level dropdown or permission settings to identify if they are set to a misconfigured or overly permissive level.
    Affected if The access control/security level is set to a value that permits unauthenticated or low-privilege users to access sensitive administrative functions within AcyMailing.
  3. Inspect user group permissions
    Go to Joomla System > Global Configuration > Permissions, and separately check the AcyMailing-specific permissions under Components > AcyMailing > Configure. Review which user groups have permission to access configuration, list management, or campaign creation features.
    Affected if Any user group other than Super Users or explicitly authorized administrators has been granted elevated permissions that allow access to sensitive AcyMailing operations.
  4. Check for publicly accessible AcyMailing endpoints
    Review the site configuration and .htaccess rules to determine if AcyMailing front-end URLs (such as task=..., ctrl=..., or routing-based endpoints) are accessible without authentication. Attempt to access common AcyMailing task URLs without logging in.
    Affected if AcyMailing functional endpoints are accessible without authentication, allowing unauthenticated users to trigger sensitive operations.

A user is affected if their AcyMailing installation is version 10.11.1 or lower AND the access control or security level configuration permits unauthorized or unauthenticated users to access sensitive AcyMailing functionality.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks on all sensitive endpoints and functions within AcyMailing, ensuring that access is restricted based on user roles and permissions. Review and enforce the principle of least privilege across the application's access control configuration.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57740 — 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-2026-57740 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