AcmailerApplication · Seeds

CVE-2015-2971

MEDIUM · 5.5 CVSS v2.0 Published 2015-07-19
Fix available
A fix is available. Upgrade to 3.8.18 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Directory traversal vulnerability in Seeds acmailer before 3.8.18 and 3.9.x before 3.9.12 Beta allows remote authenticated users to delete arbitrary files via a crafted string.

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 · moderate confidence

A directory traversal vulnerability in Seeds acmailer versions before 3.8.18 and 3.9.12 Beta allows remote authenticated users to delete arbitrary files on the server by submitting crafted file path strings containing traversal sequences (such as ../../../). The vulnerability requires authentication but permits a privileged user to escape the intended directory constraints and delete files outside the application's web root.

MitigationUpdate acmailer to version 3.8.18 or 3.9.12 Beta or later to obtain the vendor patch. Additionally, restrict file deletion permissions for the web application user and implement input validation to block path traversal sequences.

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
AcmailerApplication
Affected:< 3.8.18= 3.9.0= 3.9.1= 3.9.2= 3.9.3= 3.9.4= 3.9.5= 3.9.6= 3.9.7= 3.9.8= 3.9.9= 3.9.10

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
Authentication
Single
Confidentiality
None
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:N/I:P/A:P

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 acmailer installation and identify the version
    Check your web server for the acmailer application directory. Look for a version file, changelog, or the main acmailer script that displays or contains the version number. Common locations include the root web directory or a subdirectory named 'acmailer', 'mailer', or similar.
    Affected if The installed version is lower than 3.8.18, or is version 3.9.0 through 3.9.10 inclusive.
  2. Verify the file deletion module is accessible
    Determine if the file deletion or attachment management feature of acmailer is enabled and accessible within the application. Check the application's feature configuration or admin panel for mail attachment or file management modules.
    Affected if The file deletion feature is enabled and accessible to authenticated users.
  3. Confirm authentication is possible
    Verify that user accounts exist with access to the acmailer application. The vulnerability requires an authenticated session to exploit the directory traversal in the file deletion function.
    Affected if There are active user accounts that can log into the acmailer application.
  4. Inspect file permission controls
    Review the application's file deletion functionality to determine if path traversal sequences are being validated or filtered. Check whether the deletion feature restricts operations to an intended directory or allows arbitrary paths.
    Affected if The file deletion feature does not properly sanitize or validate path input, allowing traversal sequences to pass through unchecked.

You are affected if acmailer version is below 3.8.18 or between 3.9.0 and 3.9.10, the file deletion module is enabled, and user authentication is available for the application.

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.

From vendor data
Upgrade available Upgrade to 3.8.18 or later
Fixed in 3.8.18
Interim mitigation

Update acmailer to version 3.8.18 or 3.9.12 Beta or later to obtain the vendor patch. Additionally, restrict file deletion permissions for the web application user and implement input validation to block path traversal sequences.

Fix this in Acmailer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-2971 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-2971 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