CVE-2022-29303
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 · uneditedSolarView Compact ver.6.00 was discovered to contain a command injection vulnerability via conf_mail.php.
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 confidenceSolarView Compact version 6.00 contains a command injection vulnerability in conf_mail.php that allows remote attackers to execute arbitrary operating system commands via unspecified vectors. The critical CVSS score of 9.8 indicates the vulnerability is easily exploitable and results in complete compromise of the affected system.
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= 6.00CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SolarView Compact device modelCheck the device model or firmware identification - look for Contec Sv Cpt Mc310 or SolarView Compact in system information or device identification pagesAffected if Device model is Contec Sv Cpt Mc310
-
Check the firmware versionAccess the device's firmware version information page or check via administrative interface - typically found in system status, about page, or via SNMP/sysinfo queryAffected if Firmware version is exactly 6.00
-
Verify conf_mail.php is accessibleAttempt to access the URI /conf_mail.php or /php/conf_mail.php on the SolarView web interface - this is the vulnerable scriptAffected if conf_mail.php is accessible and responds to HTTP requests
-
Check if mail configuration feature is enabledExamine the SolarView web interface for mail/email configuration settings - look for SMTP configuration, email notification, or mail server settings in the admin panelAffected if Mail configuration feature is enabled and accessible to unauthenticated or low-privileged users
-
Identify exposed email input parametersReview the HTTP requests when accessing conf_mail.php - look for email-related POST/GET parameters that accept user input for SMTP server, sender, recipient, or subject fieldsAffected if The page accepts unsanitized user input in email configuration parameters
A system is affected if it is a Contec Sv Cpt Mc310 device running SolarView Compact firmware version 6.00 with the conf_mail.php mail configuration interface exposed and accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataApply input validation and sanitization to all user-supplied parameters in conf_mail.php, or upgrade to a patched version if available from the vendor. Consider network segmentation to limit exposure of the SolarView interface.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29303 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-29303 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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