CVE-2022-35239
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 · uneditedThe image file management page of SolarView Compact SV-CPT-MC310 Ver.7.23 and earlier, and SV-CPT-MC310F Ver.7.23 and earlier contains an insufficient verification vulnerability when uploading files. If this vulnerability is exploited, arbitrary PHP code may be executed if a remote authenticated attacker uploads a specially crafted PHP file.
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 confidenceThe image file management page of SolarView Compact SV-CPT-MC310 (versions 7.23 and earlier) lacks proper file validation during upload, allowing authenticated attackers to upload arbitrary PHP files. This insufficient verification of uploaded files enables remote code execution when the uploaded PHP is accessed.
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< 7.24< 7.24CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify firmware versionAccess the device web interface or check system information page. Look for firmware version displayed in the admin panel or system status section.Affected if The displayed firmware version is 7.23 or earlier, or any version below 7.24.
-
Confirm image file management feature existsNavigate to the image file management page within the web interface. This is typically found under maintenance, settings, or upload sections of the admin panel.Affected if The image file management upload page is present and accessible after authentication.
-
Verify web interface accessibilityAttempt to access the SolarView Compact administration interface via HTTP/HTTPS on the device IP address.Affected if The web administrative interface is reachable on the network.
-
Check authentication statusDetermine whether default credentials are in use or if any valid user account exists on the system.Affected if Any valid credentials can be obtained or default credentials are still active, allowing login to the image file management page.
You are affected if your device runs firmware version 7.23 or earlier (below 7.24) and the image file management upload feature is accessible after authentication.
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.
dbcve · scoped7.24
Implement strict file upload validation: whitelist allowed file extensions and MIME types, verify file magic bytes/content, rename uploaded files, and store them outside the web root. Update to version 7.30 or later which patches this vulnerability.
SolarView Compact SV-CPT-MC310 and SV-CPT-MC310F Firmware version 7.24
- Obtain SolarView Compact firmware version 7.24 or later from the official vendor website (www.contec.com)
- Access the SolarView Compact device administration interface
- Navigate to the firmware update section
- Upload and install the firmware version 7.24 following the vendor's official upgrade instructions
- Verify the firmware was successfully upgraded by checking the version in the device interface
- Restart the device if required by the upgrade process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35239 — 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-35239 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