dbcve.org
AcymailingApplication

CVE-2026-56292

HIGH · 7.5 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to 10.11.1 or later.
See remediation →
84/100
Remediation priority · High
Public exploit Remotely reachable No privileges Zero-click 6 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
Joomla Extension - acymailing.com - SQL Injection in AcyMailing extension < 10.11.1 - A SQLi vulnerability in AcyMailing component < 10.11.1 for Joomla was discovered. Exploiting this flaw can lead to unauthorized database access and data leakage.

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

SQL injection vulnerability in AcyMailing extension for Joomla versions prior to 10.11.1 allows attackers to inject malicious SQL queries through unsanitized input parameters, potentially leading to unauthorized database access and sensitive data exfiltration.

MitigationUpgrade AcyMailing to version 10.11.1 or later to remediate the SQL injection vulnerability. Alternatively, disable the extension until patching is possible.

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:>= 6.0.0, < 10.11.1

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. Locate the AcyMailing version in Joomla admin
    Log into the Joomla administrator panel, navigate to Components > AcyMailing, and find the version number displayed on the main AcyMailing dashboard or in the About section
    Affected if The displayed version is 6.0.0 through 10.11.0 (any version >= 6.0.0 but < 10.11.1)
  2. Check version via filesystem
    If access to the server is available, locate the AcyMailing manifest or version file. Common paths include /administrator/components/com_acymailing/acyhelper.php or look for a version.xml or manifest.xml within the com_acymailing directory in /administrator/components/
    Affected if The version file shows a version between 6.0.0 and 10.11.0 inclusive
  3. Query the Joomla extensions table
    Access the Joomla database (typically via phpMyAdmin or command line) and run: SELECT * FROM #__extensions WHERE element = 'acymailing' AND folder = 'system'; (replace #_ with your database prefix)
    Affected if The manifest_cache column shows a version between 6.0.0 and 10.11.0 inclusive

The environment is affected if AcyMailing version is 6.0.0 or higher but lower than 10.11.1.

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 10.11.1 or later
Fixed in 10.11.1
Interim mitigation

Upgrade AcyMailing to version 10.11.1 or later to remediate the SQL injection vulnerability. Alternatively, disable the extension until patching is possible.

Recommended fix High confidence

10.11.1

  1. Backup your Joomla site and database before performing any upgrade
  2. Download AcyMailing version 10.11.1 from the official AcyMailing website (www.acymailing.com) or from mysites.guru
  3. Log in to your Joomla administration panel
  4. Navigate to Extensions > Manage > Install
  5. Upload and install the AcyMailing 10.11.1 package
  6. After installation, verify the installed version by going to Components > AcyMailing and confirming the version number
  7. Clear any Joomla and browser caches
  8. Test critical AcyMailing functionality (sending newsletters, managing lists, subscriber imports) to ensure the upgrade did not break existing functionality
Caveat Review AcyMailing's changelog between your current version and 10.11.1 for any feature changes or deprecations that may affect your workflows

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

Fix this in Acymailing Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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