AcymailingApplication
CVE-2023-28733
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 · uneditedAnyMailing Joomla Plugin is vulnerable to stored cross site scripting (XSS) in templates and emails of AcyMailing, exploitable without authentication when access is granted to the campaign's creation on front-office. This issue affects AnyMailing Joomla Plugin Enterprise 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 confidenceAnyMailing Joomla Plugin Enterprise versions before 8.3.0 contain a stored cross-site scripting (XSS) vulnerability in the email template functionality. Attackers with front-office campaign creation access can inject malicious JavaScript into templates and emails, which executes when recipients view the crafted emails or administrators manage those templates.
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
< 8.3.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 the installed Acymailing versionNavigate to Components > Acymailing in the Joomla admin panel and locate the version number in the component information or about page. Alternatively, check the version in the manifest file at /administrator/components/com_acymailing/acymailing.xml or via the Joomla extensions manager.Affected if The installed version is any version before 8.3.0 (e.g., 8.2.x, 8.1.x, 8.0.x, or earlier)
-
Confirm front-office campaign creation access is enabledIn the Acymailing component, go to Configuration > Frontend Access or Users > Levels to verify if front-office users have permission to create or edit email templates and campaigns.Affected if Front-office campaign creation or template editing permissions are granted to any user group beyond administrators
-
Inspect email templates for suspicious contentNavigate to Acymailing > Templates or Mail section in the admin panel and review all email templates for unexpected script tags, javascript: URIs, onload/onerror attributes, or base64-encoded payloads that could indicate XSS injection.Affected if Any email template contains executable JavaScript code, event handler attributes, or suspicious encoded content that was not intentionally added by administrators
-
Check email campaign configurations for injected contentReview the campaign and newsletter listings in Acymailing, examining the subject lines, content body, and HTML source for any injected script elements or unusual HTML that does not match legitimate business communications.Affected if Campaigns or emails contain JavaScript code, iframe elements, or other potentially malicious content not created by authorized administrators
You are affected if your Acymailing installation is any version before 8.3.0 and the email template or campaign functionality is accessible to users who could inject malicious content.
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.3.0
Upgrade AnyMailing Joomla Plugin Enterprise to version 8.3.0 or later to remediate this stored XSS vulnerability.
Acymailing Enterprise 8.3.0 or later
- 1. Log in to the Joomla administrator dashboard
- 2. Navigate to Components > AcyMailing
- 3. Check the current installed version under AcyMailing > Configuration or About section
- 4. If version is below 8.3.0, navigate to Extensions > Manage > Update
- 5. Click 'Find Updates' to refresh the extension update list
- 6. Locate Acymailing in the update list and select it
- 7. Click 'Update' to install version 8.3.0 or later
- 8. After update completes, verify the new version is 8.3.0 or higher
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
- 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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28733 — 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-28733 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