Is there a public exploit for CVE-2026-56292?

Yes. Proof-of-concept code for CVE-2026-56292 has been published publicly.

Is there a proof of concept for CVE-2026-56292?

Yes — 1 proof-of-concept entry is linked on this page, from public repositories and community submissions. They are listed for authorised testing only.

How severe is CVE-2026-56292?

CVE-2026-56292 scores CVSS 9.2 (v4.0), rated critical. EPSS puts the chance of exploitation in the next 30 days at 1.38%.

What does CVE-2026-56292 affect?

CVE-2026-56292 affects Datasolution acymailing.com AcyMailing extension for Joomla.

9.2 Critical

Joomla Extension - acymailing.com - SQL Injection in AcyMailing extension < 10.11.1 - A SQLi vulnerability in AcyMailing component <…

CVE-2026-56292

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.

Proof-of-concept code is published

Public PoC · Nuclei template

NucleiAcyMailing < 10.11.1 - Unauthenticated SQL Injection
Public PoCnullwhisper/CVE-2026-56292-AcyMailing-SQLi3 stars

A Nuclei detection template exists for this, which means it is scanned for at internet scale rather than looked for deliberately.

Signals come from Exploit-DB, Metasploit, Nuclei and published proof-of-concept repositories. Their absence means nothing was found, not that nothing exists.

Assessment

CVSS: 9.2 (v4.0)
Severity: Critical
EPSS: 1.38% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Public PoC, Nuclei template
Published: 9 July 2026
Last updated: 12 November 2026
Affected: Datasolution · acymailing.com AcyMailing extension for Joomla
Assigner: Joomla

CVSS vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:L/SC:H/SI:H/SA:H

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 9 + 4? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-56292