JVNDB-2025-000086

Vulnerability from jvndb - Published: 2025-10-15 06:54 - Updated:2025-10-15 06:54
Severity
Summary
Phoenix Contact CHARX SEC-3xxx vulnerable to code injection
Details
CHARX SEC-3xxx provided by Phoenix Contact contains the following vulnerability.
  • Code injection (CWE-94) - CVE-2025-41699
Ryo Kato of Panasonic Holdings Corporation reported this vulnerability to IPA. JPCERT/CC coordinated with the developer under Information Security Early Warning Partnership.
Show details on JVN DB website

{
  "@rdf:about": "https://jvndb.jvn.jp/en/contents/2025/JVNDB-2025-000086.html",
  "dc:date": "2025-10-15T15:54+09:00",
  "dcterms:issued": "2025-10-15T15:54+09:00",
  "dcterms:modified": "2025-10-15T15:54+09:00",
  "description": "CHARX SEC-3xxx provided by Phoenix Contact contains the following vulnerability.\r\n\u003cul\u003e\u003cli\u003eCode injection (CWE-94) - CVE-2025-41699\u003c/li\u003e\u003c/ul\u003e\r\nRyo Kato of Panasonic Holdings Corporation reported this vulnerability to IPA.\r\nJPCERT/CC coordinated with the developer under Information Security Early Warning Partnership.",
  "link": "https://jvndb.jvn.jp/en/contents/2025/JVNDB-2025-000086.html",
  "sec:cpe": [
    {
      "#text": "cpe:/o:phoenixcontact:charx_sec-3000_firmware",
      "@product": "charx sec-3000 firmware",
      "@vendor": "PHOENIX CONTACT",
      "@version": "2.2"
    },
    {
      "#text": "cpe:/o:phoenixcontact:charx_sec-3050_firmware",
      "@product": "charx sec-3050 firmware",
      "@vendor": "PHOENIX CONTACT",
      "@version": "2.2"
    },
    {
      "#text": "cpe:/o:phoenixcontact:charx_sec-3100_firmware",
      "@product": "charx sec-3100 firmware",
      "@vendor": "PHOENIX CONTACT",
      "@version": "2.2"
    },
    {
      "#text": "cpe:/o:phoenixcontact:charx_sec-3150_firmware",
      "@product": "charx sec-3150 firmware",
      "@vendor": "PHOENIX CONTACT",
      "@version": "2.2"
    }
  ],
  "sec:cvss": {
    "@score": "8.8",
    "@severity": "High",
    "@type": "Base",
    "@vector": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
    "@version": "3.0"
  },
  "sec:identifier": "JVNDB-2025-000086",
  "sec:references": [
    {
      "#text": "https://jvn.jp/en/jp/JVN42282226/index.html",
      "@id": "JVN#42282226",
      "@source": "JVN"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2025-41699",
      "@id": "CVE-2025-41699",
      "@source": "CVE"
    },
    {
      "#text": "https://certvde.com/en/advisories/VDE-2025-074/",
      "@id": "VDE-2025-074: Phoenix Contact: Security Advisory for CHARX SEC-3xxx charging controllers",
      "@source": "Related Information"
    },
    {
      "#text": "https://www.ipa.go.jp/en/security/vulnerabilities/cwe.html",
      "@id": "CWE-94",
      "@title": "Code Injection(CWE-94)"
    }
  ],
  "title": "Phoenix Contact CHARX SEC-3xxx vulnerable to code injection"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…