Skip to main content
VulnerabilityPublished

CVE-2025-8319: Barracuda Message Archiver · Cross-site Scripting

Affects Barracuda Message ArchiverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Barracuda Barracuda Message ArchiverAffected
  • =5.4.2.002
Fixed in–

AI-suggested

European organizations should prioritize the following specific mitigation steps: 1) Upgrade or patch the Barracuda Message Archiver to a version where this vulnerability is fixed as soon as a patch is released by Barracuda. In the absence of an official patch, consider applying virtual patching via Web Application Firewalls (WAF) to filter or sanitize requests containing the 'error=' parameter. 2) Implement strict input validation and output encoding on the login interface to neutralize any injected scripts. 3) Educate users about the risks of clicking on suspicious links, especially those purporting to be error messages or login pages. 4) Monitor web server logs for unusual or suspicious URL parameters that include script tags or encoded payloads targeting the 'error=' parameter. 5) Employ Content Security Policy (CSP) headers to restrict the execution of inline scripts and reduce the impact of potential XSS attacks. 6) Review and tighten session management controls to limit the damage from session hijacking attempts. 7) Conduct regular security assessments and penetration tests focusing on web interface vulnerabilities to detect similar issues proactively.

Description

the BMA login interface allows arbitrary JavaScript or HTML to be written straight into the page’s Document Object Model via the error= URL parameter

References

Community reviews

Loading reviews…