dbcve.org
Sv Cpt Mc310f FirmwareOperating system · Contec

CVE-2023-27521

HIGH · 8.8 CVSS v3.1 Published 2023-05-23
Fix available
A fix is available. Upgrade to 8.10 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
OS command injection vulnerability in the mail setting page of SolarView Compact SV-CPT-MC310 versions prior to Ver.8.10 and SV-CPT-MC310F versions prior to Ver.8.10 allows remote authenticated attackers to execute an arbitrary OS command.

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

OS command injection vulnerability in the mail settings page of SolarView Compact SV-CPT-MC310 and SV-CPT-MC310F allows remote authenticated attackers to inject and execute arbitrary OS commands through unsanitized input fields in the mail configuration functionality.

MitigationUpdate to version 8.10 or later to patch the command injection flaw. If immediate update is not feasible, restrict network access to the management interface and review logs for suspicious mail configuration activity.

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
Sv Cpt Mc310f FirmwareOperating system
Affected:< 8.10
Sv Cpt Mc310 FirmwareOperating system
Affected:< 8.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
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. Identify device firmware version
    Log into the SolarView Compact web management interface (typically at the device IP address) and navigate to the System Information or Status page to view the installed firmware version. Alternatively, check the firmware version via the device's administrative console or About page.
    Affected if The firmware version is lower than 8.10 (for example, 8.09, 8.08, or earlier releases).
  2. Verify mail configuration functionality is accessible
    Access the mail settings or email configuration page within the device's web interface. This is typically found under Settings, Network Settings, or Maintenance sections. Confirm the page loads and accepts input.
    Affected if The mail settings page is present and accessible, indicating the vulnerable feature is enabled on the device.
  3. Check network exposure of management interface
    Determine if the SolarView management web interface is directly accessible from untrusted networks (such as the internet or guest networks) by reviewing firewall rules, NAT configurations, or port forwarding settings on upstream network devices.
    Affected if The management interface is exposed to untrusted networks without proper access controls or VPN protection.
  4. Review logs for suspicious mail configuration activity
    Examine the device logs or system logs accessible through the web interface for entries related to mail configuration, particularly those containing unexpected characters, multiple failed attempts, or commands that appear malformed.
    Affected if Log entries show unusual or malformed input in mail-related fields, or suspicious command execution patterns originating from mail configuration saves.

A user is affected if the device runs firmware version below 8.10 and has the mail configuration feature accessible, particularly if the management interface is exposed to untrusted networks.

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

Update to version 8.10 or later to patch the command injection flaw. If immediate update is not feasible, restrict network access to the management interface and review logs for suspicious mail configuration activity.

Recommended fix High confidence

Firmware Ver.8.10 or later for both SV-CPT-MC310 and SV-CPT-MC310F

  1. 1. Identify the current firmware version of the SolarView Compact SV-CPT-MC310 or SV-CPT-MC310F device
  2. 2. Navigate to the official CONTEC support website (www.contec.com) to download firmware version 8.10 or later
  3. 3. Follow the vendor's provided firmware update procedure to upgrade the device to version 8.10 or newer
  4. 4. After completing the upgrade, verify that the device is now running firmware version 8.10 or later to confirm the vulnerability is remediated

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

Fix this in Sv Cpt Mc310f Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
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,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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