dbcve.org
InjectionWeakness · CWE-74

CVE-2026-12223

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
A vulnerability was identified in Yealink SIP-T46U 108.86.0.118. Affected by this vulnerability is the function mod_webd.TFTPUploadIperf of the file /api/inner/tftpuploadiperf of the component Web FastCGI Service. The manipulation of the argument ip/port leads to command injection. The attack needs to be initiated within the local network. The exploit is publicly available and might be used. Upgrading to version 108.87.0.23 addresses this issue. Upgrading the affected component is recommended. The vendor explains: "It has been fixed (...) for our technical support branch. However, please note that this specific support branch firmware is not publicly released yet."

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

Command injection vulnerability in Yealink SIP-T46U phones allows remote attackers within the local network to execute arbitrary commands via the ip/port arguments in the /api/inner/tftpuploadiperf endpoint of the Web FastCGI Service.

MitigationUpgrade firmware to version 108.87.0.23; however, note that the fixed version is currently only available through Yealink's technical support branch and not publicly released, so contact vendor for access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 device model
    Access the phone's web interface or check the device label/menu to confirm the model is Yealink SIP-T46U
    Affected if Device model is not Yealink SIP-T46U (not affected)
  2. Check the firmware version
    Navigate to the phone web interface Status or Settings page, or access the device via SSH/TFTP to retrieve the firmware version
    Affected if Firmware version is exactly 108.86.0.118 (vulnerable) or any version below the patched release
  3. Verify the Web FastCGI Service is enabled
    Check if the phone's web interface is accessible on the network by attempting to reach the device's IP address on port 80 or 443
    Affected if Web interface is not accessible (reduced attack surface but does not indicate if the vulnerability is patched)
  4. Confirm the vulnerable endpoint exists
    Send an HTTP request to /api/inner/tftpuploadiperf on the device's web interface (requires authentication if enabled)
    Affected if Endpoint returns any response (indicates the service is running and potentially vulnerable if firmware version is 108.86.0.118)

The device is affected if it is a Yealink SIP-T46U running firmware version 108.86.0.118 with the web interface accessible on the local network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade firmware to version 108.87.0.23; however, note that the fixed version is currently only available through Yealink's technical support branch and not publicly released, so contact vendor for access.

Recommended fix Moderate confidence

Yealink SIP-T46U firmware version 108.87.0.23

  1. Identify the exact firmware version of the Yealink SIP-T46U device by accessing the web interface or checking system information
  2. Navigate to Yealink's official support portal or contact Yealink technical support to obtain firmware version 108.87.0.23
  3. Back up the current device configuration before performing the firmware upgrade
  4. Upload and apply firmware version 108.87.0.23 through the device's web management interface or provisioning system
  5. Verify the upgrade was successful and the device is functioning normally
  6. Confirm the vulnerability is remediated by testing that the /api/inner/tftpuploadiperf endpoint no longer accepts command injection in the ip/port parameters

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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