dbcve.org
Energy Axc PuApplication · Phoenixcontact

CVE-2023-1109

HIGH · 8.8 CVSS v3.1 Published 2023-04-17
Fix available
A fix is available. Upgrade to after 04.15.00.00 or later.
See remediation →
94/100
Remediation priority · Urgent
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
In Phoenix Contacts ENERGY AXC PU Web service an authenticated restricted user of the web frontend can access, read, write and create files throughout the file system using specially crafted URLs via the upload and download functionality of the web service. This may lead to full control of the service.

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

A path traversal vulnerability in Phoenix Contacts ENERGY AXC PU Web service allows authenticated restricted users to access, read, write, and create files throughout the filesystem via specially crafted URLs in the upload and download functionality. This enables full service compromise.

MitigationApply vendor patch when available; until then, restrict network access to the web service, enforce strict authentication controls, and monitor for suspicious URL patterns in upload/download requests.

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
Energy Axc PuApplication
Affected:>= 01.00.00.00, <= 04.15.00.00
Infobox FirmwareOperating system
Affected:>= 01.00.00.00, <= 02.02.00.00
Smartrtu Axc Sg FirmwareOperating system
Affected:>= 01.00.00.00, <= 01.08.00.02
Smartrtu Axc Ig FirmwareOperating system
Affected:>= 01.00.00.00, <= 01.02.00.01

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the web service endpoint
    Locate the ENERGY AXC PU web service by accessing its HTTP/HTTPS interface on the network. Typically runs on ports 80/443 or custom ports. Note the device's IP address and confirm the web interface is reachable.
    Affected if The web service is accessible from the network without firewall restrictions.
  2. Determine the installed firmware version
    Log into the web interface and navigate to the system information or firmware version page. Compare the displayed version number against the affected ranges: Energy Axc Pu (01.00.00.00 - 04.15.00.00), Infobox Firmware (01.00.00.00 - 02.02.00.00), Smartrtu Axc Sg (01.00.00.00 - 01.08.00.02), Smartrtu Axc Ig (01.00.00.00 - 01.02.00.01).
    Affected if The installed version falls within any of the listed affected version ranges.
  3. Verify if upload and download features are accessible
    Check if the web interface includes file upload or download functionality, typically found in file management, configuration backup, or firmware update sections. These are the attack vectors for path traversal.
    Affected if The upload or download functionality is enabled and accessible to authenticated users.
  4. Review user account privileges
    Examine the web service user accounts and confirm whether restricted or low-privilege user accounts exist. The vulnerability affects authenticated restricted users.
    Affected if Non-administrator or restricted user accounts are present and have access to the upload/download features.
  5. Inspect web server logs for suspicious URL patterns
    Review the device or proxy logs for requests containing path traversal sequences such as '../' or '..\' in upload/download endpoints. These patterns indicate exploitation attempts.
    Affected if Logs show path traversal patterns in requests to upload or download functionality.

You are affected if the ENERGY AXC PU web service is exposed, the installed firmware version falls within the listed ranges, and upload/download functionality is accessible to authenticated users.

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
Upgrade available Upgrade to a release after 04.15.00.00
Interim mitigation

Apply vendor patch when available; until then, restrict network access to the web service, enforce strict authentication controls, and monitor for suspicious URL patterns in upload/download requests.

Fix this in Energy Axc Pu Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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