dbcve.org
AcmailerApplication · Seeds

CVE-2016-1142

CRITICAL · 9.1 CVSS v3.0 Published 2016-01-16
Fix available
A fix is available. Upgrade to 3.8.21 or later.
See remediation →
97/100
Remediation priority · Urgent
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
Seeds acmailer before 3.8.21 and 3.9.x before 3.9.15 Beta allows remote authenticated users to execute arbitrary OS commands via unspecified vectors.

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

Command injection vulnerability in acmailer email marketing software versions before 3.8.21 and 3.9.x before 3.9.15 Beta allows remote authenticated users to execute arbitrary operating system commands on the hosting server through unspecified vectors.

MitigationUpgrade acmailer to version 3.8.21 or later (or 3.9.15 Beta or later for the 3.9.x branch) to remediate the command injection vulnerability.

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.0, < 3.8.21= 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
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

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 acmailer installation
    Identify the web root directory where acmailer email marketing software is installed. Look for the main application files such as index.php or an acmailer subdirectory.
    Affected if acmailer is present in the environment
  2. Determine acmailer version
    Find the version information in the application. Check common version disclosure locations such as a version file, README file, or the main index file header that displays the software version. Compare the found version against the affected ranges.
    Affected if the installed version is 3.8.0 through 3.8.20, or exactly one of 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, or 3.9.10
  3. Confirm authentication is accessible
    Determine whether the acmailer web interface has remote user authentication enabled. Review configuration files or test whether login functionality is accessible to remote users.
    Affected if remote unauthenticated or authenticated access to the acmailer interface is possible and the version falls within the affected ranges

The environment is affected if acmailer is installed with a version between 3.8.0 and 3.8.20 inclusive, or any of the specific 3.9.x versions from 3.9.0 through 3.9.10, and remote users can access the application interface.

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.

dbcve · scoped
Upgrade available Upgrade to 3.8.21 or later
Fixed in 3.8.21
Interim mitigation

Upgrade acmailer to version 3.8.21 or later (or 3.9.15 Beta or later for the 3.9.x branch) to remediate the command injection vulnerability.

Recommended fix High confidence

Acmailer 3.8.21 or later for 3.8.x branch; Acmailer 3.9.15 Beta or later for 3.9.x branch

  1. 1. Identify the currently installed Acmailer version by checking the software's about page or version file
  2. 2. For Acmailer 3.8.x users (versions 3.8.0 through 3.8.20): Download and install Acmailer version 3.8.21 or later from the official vendor website (www.acmailer.jp)
  3. 3. For Acmailer 3.9.x users (versions 3.9.0 through 3.9.14): Download and install Acmailer version 3.9.15 Beta or later from the official vendor website (www.acmailer.jp)
  4. 4. After upgrade, verify the new version is correctly installed
  5. 5. Test that the application functions normally after the upgrade
  6. 6. Review any configuration changes required between versions using vendor release notes
Caveat Review vendor release notes for potential breaking changes between versions; Beta version (3.9.15 Beta) may have unstability risks

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Acmailer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2016-1142 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