Saj Solar InverterApplication · Saj Electric

CVE-2018-12735

HIGH · 7.5 CVSS v3.0 Published 2018-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
SAJ Solar Inverter allows remote attackers to obtain potentially sensitive information via a direct request for the inverter_info.htm or english_main.htm URI.

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

SAJ Solar Inverter web interface contains information disclosure vulnerability where sensitive data can be exposed via direct HTTP requests to inverter_info.htm or english_main.htm pages without proper authentication or authorization controls.

MitigationImplement proper access control and authentication requirements on sensitive web pages, or remove sensitive information from these endpoints. Consider network segmentation to limit exposure of the inverter management interface.

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
Saj Solar InverterApplication
Affected:all versions

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

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

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. Confirm Saj Solar Inverter is in use
    Identify if the target environment contains a Saj Electric Saj Solar Inverter device. Check network inventory, device labels, or documentation for this specific product.
    Affected if The environment includes a Saj Electric Saj Solar Inverter device.
  2. Locate the web management interface
    Identify the IP address or hostname of the inverter's web interface. This is typically accessible on the local network via HTTP on port 80 or 8080.
    Affected if A web interface for the Saj Solar Inverter is reachable on the network.
  3. Test inverter_info.htm for unauthenticated access
    Using a web browser or curl command, navigate directly to http://<inverter-ip>/inverter_info.htm without providing any login credentials. Observe if the page loads and displays any information.
    Affected if The inverter_info.htm page loads and displays data without requiring authentication.
  4. Test english_main.htm for unauthenticated access
    Using a web browser or curl command, navigate directly to http://<inverter-ip>/english_main.htm without providing any login credentials. Observe if the page loads and displays any information.
    Affected if The english_main.htm page loads and displays data without requiring authentication.
  5. Verify sensitive data exposure
    Examine the content returned from either page. Look for system configuration details, operational parameters, network settings, or other sensitive information that should require authentication to access.
    Affected if Either page reveals sensitive inverter data such as configuration, performance metrics, or network details without authentication.

If a Saj Solar Inverter web interface is accessible and either inverter_info.htm or english_main.htm pages return data without authentication, the environment is affected by CVE-2018-12735.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper access control and authentication requirements on sensitive web pages, or remove sensitive information from these endpoints. Consider network segmentation to limit exposure of the inverter management interface.

Fix this in Saj Solar Inverter Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-12735 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-12735 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