dbcve.org
Network Shutdown ModuleHardware / appliance · Eaton

CVE-2008-6816

HIGH · 10.0 CVSS v2.0 Published 2009-05-28
Fix available
A fix is available. Upgrade to after 3.1_beta or later.
See remediation →
100/100
Remediation priority · Urgent
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
Eaton MGEOPS Network Shutdown Module before 3.10 Build 13 allows remote attackers to execute arbitrary code by adding a custom action to the MGE frontend via pane_actionbutton.php, and then executing this action via exec_action.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 · high confidence

Unauthenticated remote code execution vulnerability in Eaton MGEOPS Network Shutdown Module versions before 3.10 Build 13. Attackers inject arbitrary commands by adding a custom action through pane_actionbutton.php and executing it via exec_action.php, achieving full system compromise.

MitigationUpgrade to MGEOPS version 3.10 Build 13 or later. If immediate patching is not feasible, restrict network access to the management interface using network segmentation or firewall rules.

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
Network Shutdown ModuleHardware / appliance
Affected:<= 3.1_beta= 2.6= 3.0= 3.02= 3.04

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 the installed version of Eaton Network Shutdown Module
    Locate the version information through the application's web interface (typically in Help > About or System Info), check configuration files, or query the installed software on the host system
    Affected if The version displayed is 3.1_beta or lower, 2.6, 3.0, 3.02, or 3.04 (these match the affected versions listed)
  2. Verify the presence of the vulnerable PHP scripts
    Check the web server document root for the existence of pane_actionbutton.php and exec_action.php files in the application's web directory
    Affected if These PHP files exist in the web-accessible directory, indicating the vulnerable code is present
  3. Confirm the web management interface is accessible
    Attempt to access the MGEOPS web interface over HTTP/HTTPS from a network location or verify the service is listening on the expected port (typically port 80/443 or a custom management port)
    Affected if The web interface responds to requests, meaning it is network-accessible and the attack surface is exposed
  4. Check for unauthenticated access to action scripts
    Review web server access logs or attempt a test request to pane_actionbutton.php and exec_action.php without authentication credentials
    Affected if These endpoints are reachable without authentication, matching the unauthenticated attack vector described

If the installed version falls within 2.6, 3.0, 3.02, 3.04, 3.1_beta or earlier AND the web management interface with the vulnerable PHP scripts is network-accessible, the environment is affected by this CVE.

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 a release after 3.1_beta
Interim mitigation

Upgrade to MGEOPS version 3.10 Build 13 or later. If immediate patching is not feasible, restrict network access to the management interface using network segmentation or firewall rules.

Recommended fix High confidence

Eaton MGEOPS Network Shutdown Module version 3.10 Build 13 or later

  1. 1. Identify the current version of the Eaton MGEOPS Network Shutdown Module installed on the system
  2. 2. Download version 3.10 Build 13 or later from the official Eaton/download.mgeops.com repository
  3. 3. Review the upgrade documentation specific to the MGEOPS Network Shutdown Module
  4. 4. Perform a full backup of the current configuration and any custom settings
  5. 5. Stop the Network Shutdown Module service before upgrading
  6. 6. Install version 3.10 Build 13 or later following the vendor's upgrade procedure
  7. 7. Verify the installation was successful by checking the version number
  8. 8. Restart the Network Shutdown Module service
Caveat Major version upgrades may introduce configuration changes or deprecate features; review release notes before upgrading and test in a non-production environment

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

Fix this in Network Shutdown Module Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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