dbcve.org
Port MysApplication · Liman

CVE-2021-3855

HIGH · 8.8 CVSS v3.1 Published 2023-03-01
Fix available
A fix is available. Upgrade to 1.8.3-462 or later.
See remediation →
94/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
Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Liman Central Management System Liman MYS (HTTP/Controllers, CronMail, Jobs modules) allows Command Injection. This issue affects Liman Central Management System: from 1.7.0 before 1.8.3-462.

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 confidence

Command injection vulnerability in Liman Central Management System affecting HTTP/Controllers, CronMail, and Jobs modules in versions 1.7.0 through before 1.8.3-462 allows attackers to execute arbitrary commands via improper neutralization of special elements in these components.

MitigationUpgrade Liman CMS to version 1.8.3-462 or later which includes the patch for this 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
Port MysApplication
Affected:>= 1.7.0, < 1.8.3-462

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Check installed Liman CMS version
    Access the Liman web interface and navigate to the admin panel or settings page to view the system version information. Alternatively, check the application source files for version metadata (e.g., version file, composer.json, or about page).
    Affected if The installed version is 1.7.0 or any version from 1.7.0 up to but not including 1.8.3-462
  2. Verify CronMail module is enabled
    Check if the CronMail functionality is accessible in the Liman CMS dashboard or configuration. Look for mail-related scheduled task or cron job features within the system administration interface.
    Affected if The CronMail module is present and enabled, and the version is in the affected range
  3. Verify Jobs module is accessible
    Navigate to the Jobs section in the Liman CMS admin panel to confirm the module is available. Check for any job scheduling or task execution features.
    Affected if The Jobs module is accessible and the version is in the affected range
  4. Check HTTP/Controllers endpoint exposure
    Inspect the application's web routes and controller files to confirm the HTTP/Controllers are exposed. Look for any web-accessible endpoints in the Liman installation directory.
    Affected if HTTP/Controllers endpoints are exposed via web and the version is in the affected range

A user is affected if the installed Liman CMS version is between 1.7.0 and 1.8.3-462 (exclusive) and any of the CronMail, Jobs, or HTTP/Controllers modules are enabled and accessible.

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 1.8.3-462 or later
Fixed in 1.8.3-462
Interim mitigation

Upgrade Liman CMS to version 1.8.3-462 or later which includes the patch for this command injection vulnerability.

Recommended fix Moderate confidence

1.8.3-462

  1. Identify the currently installed Liman MYS version using the web interface or command line tools
  2. Backup the current Liman MYS installation and database before proceeding with the upgrade
  3. Upgrade Liman MYS to version 1.8.3-462 or later to remediate the command injection vulnerability
  4. Verify the upgrade was successful by checking the version in the administration panel
  5. Test that the HTTP/Controllers, CronMail, and Jobs modules function correctly after upgrade
  6. Review system logs to confirm no exploitation attempts occurred prior to the upgrade

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

Fix this in Port Mys Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-3855 — 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-2021-3855 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