dbcve.org
Bmxnoc0401 FirmwareOperating system · Schneider Electric

CVE-2015-6461

MEDIUM · 5.4 CVSS v3.0 Published 2019-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
Remote file inclusion allows an attacker to craft a specific URL referencing the Schneider Electric Modicon BMXNOC0401, BMXNOE0100, BMXNOE0110, BMXNOE0110H, BMXNOR0200H, BMXP342020, BMXP342020H, BMXP342030, BMXP3420302, BMXP3420302H, or BMXP342030H PLC web server, which, when launched, will result in the browser redirecting to a remote file via a Java script loaded with the web page.

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

Remote File Inclusion (RFI) vulnerability in Schneider Electric Modicon BMXNOC0401, BMXNOE0100, BMXNOE0110, BMXNOE0110H, BMXNOR0200H, BMXP342020, BMXP342020H, BMXP342030, BMXP3420302, BMXNOE0302H, and BMXP342030H PLC web servers allows attackers to craft malicious URLs that inject remote JavaScript, potentially redirecting users to attacker-controlled sites or executing client-side attacks.

MitigationApply vendor firmware updates when available; until then, restrict network access to PLC web interfaces via firewalls or network segmentation, and disable the web server if not operationally required.

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
Bmxnoc0401 FirmwareOperating system
Affected:all versions
Bmxnoe0100 FirmwareOperating system
Affected:all versions
Bmxnoe0110 FirmwareOperating system
Affected:all versions
Bmxnoe0110h FirmwareOperating system
Affected:all versions
Bmxnor0200h FirmwareOperating system
Affected:all versions
Modicon M340 Bmxp342020 FirmwareOperating system
Affected:all versions
Modicon M340 Bmxp342020h FirmwareOperating system
Affected:all versions
Modicon M340 Bmxp342030 FirmwareOperating system
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Identify if the PLC web interface is accessible
    Attempt to access the PLC web server by navigating to its IP address over HTTP (e.g., http://<PLC_IP_ADDRESS>). If a login page or web interface loads, the web server is enabled.
    Affected if The web interface is accessible on the network, making the RFI vulnerability exploitable.
  2. Confirm the PLC model
    Check the label on the physical PLC module or examine the web interface banner/page for the model number (e.g., BMXNOC0401, BMXNOE0100, BMXP342030).
    Affected if The model matches one of the affected products listed in the CVE (BMXNOC0401, BMXNOE0100, BMXNOE0110, BMXNOE0110H, BMXNOR0200H, BMXP342020, BMXP342020H, BMXP342030, or related variants).
  3. Verify the firmware version
    Log into the PLC web interface and navigate to the firmware or system information page, or use the PLC programming software (e.g., Unity Pro or EcoStruxure) to read the firmware version from the CPU module properties.
    Affected if The firmware version is any version (all versions of the affected products are vulnerable per the CVE).
  4. Check network exposure of the web server
    Review network firewall rules, VLAN configuration, or ACLs to determine whether the PLC web server (port 80/443) is exposed to untrusted networks or the internet.
    Affected if The PLC web interface is reachable from untrusted networks or directly from the internet.
  5. Inspect for suspicious URL parameters
    If you have access to PLC logs or a WAF/IDS, review logs for URL patterns containing 'http://' or 'https://' in query parameters (e.g., ?file=http://attacker.com). This may indicate exploitation attempts.
    Affected if Such patterns appear in logs, confirming the vulnerability has been targeted.

If the PLC web server is accessible and the model matches an affected BMX series product, the environment is vulnerable to CVE-2015-6461 RFI attacks.

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

Apply vendor firmware updates when available; until then, restrict network access to PLC web interfaces via firewalls or network segmentation, and disable the web server if not operationally required.

Fix this in Bmxnoc0401 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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