LiveActive security incident?Get immediate response
CVE Record

CVE-2017-9517: atmail before 7.8.0.2 has CSRF, allowing an attacker to upload and import users via CSV.

atmail before 7.8.0.2 has CSRF, allowing an attacker to upload and import users via CSV.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-9517 is a cross-site request forgery issue in atmail before 7.8.0.2. The reported impact is that an attacker could trigger a CSV user upload/import action. Business urgency depends on whether legacy atmail administration remains reachable and whether user import could alter mail access.

Executive priority

Prioritize if atmail is still used for business mail or identity-related administration. The issue is old, but legacy mail systems often persist and unauthorized user import could create access-control and compliance risk.

Technical view

The public record describes CSRF in atmail versions before 7.8.0.2, affecting CSV-based user upload/import. The sources do not provide CVSS, endpoint details, roles required, or proof-of-concept status. CSRF typically depends on a privileged victim browser, but exact preconditions are not specified.

Likely exposure

Exposure is most likely in organizations still running atmail before 7.8.0.2, especially where administrative user-import functions are reachable from browsers used by privileged staff.

Exploitation context

The supplied sources do not show CISA KEV listing or active exploitation. They also do not document exploit maturity. Treat this as a legacy product exposure requiring verification, not as confirmed internet-wide exploitation.

Researcher notes

Evidence is thin: no CVSS, CWE, CPE, endpoint, or detailed vendor remediation text is included beyond the 7.8.0.2 update reference. Do not assume affected editions or exploitability beyond atmail before 7.8.0.2.

Mitigation direction

  • Upgrade atmail to 7.8.0.2 or later where applicable.
  • Review the atmail 7.8.0.2 update guidance before changing production systems.
  • Restrict access to administrative interfaces until version status is confirmed.
  • Audit recent CSV user imports and unexpected account additions.

Validation and detection

  • Inventory atmail deployments and record exact versions.
  • Confirm no instance is older than 7.8.0.2.
  • Review user import logs for unexplained CSV activity.
  • Check whether administrative atmail functions are exposed to untrusted networks.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-9517 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.