FKIE_CVE-2025-52919

Vulnerability from fkie_nvd - Published: 2025-06-21 23:15 - Updated: 2026-06-17 09:37
Severity
4.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Summary
In Yealink RPS before 2025-05-26, the certificate upload function does not properly validate certificate content, potentially allowing invalid certificates to be uploaded.
References
cve@mitre.orghttps://dnip.ch/2025/06/25/yealink-voip-phones-insecurity-by-design/
cve@mitre.orghttps://seclists.org/fulldisclosure/2025/Jun/20
cve@mitre.orghttps://support.yealink.com/en/portal/knowledge/show?id=6476e7cd6a27da76bd06a9c9
cve@mitre.orghttps://www.yealink.com/en/trust-center/security-advisories/ecb16a4993014d22
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "RPS",
          "vendor": "Yealink",
          "versions": [
            {
              "lessThan": "2025-05-26",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "source": "cve@mitre.org"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In Yealink RPS before 2025-05-26, the certificate upload function does not properly validate certificate content, potentially allowing invalid certificates to be uploaded."
    },
    {
      "lang": "es",
      "value": "En Yealink YMCS RPS anterior al 26/05/2025, la funci\u00f3n de carga de certificados no valida correctamente el contenido del certificado, lo que potencialmente permite que se carguen certificados no v\u00e1lidos."
    }
  ],
  "id": "CVE-2025-52919",
  "lastModified": "2026-06-17T09:37:16.790",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 4.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "LOW",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 1.4,
        "source": "cve@mitre.org",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2025-52919",
          "options": [
            {
              "exploitation": "poc"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2025-06-23T14:43:45.457965Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2025-06-21T23:15:24.297",
  "references": [
    {
      "source": "cve@mitre.org",
      "url": "https://dnip.ch/2025/06/25/yealink-voip-phones-insecurity-by-design/"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://seclists.org/fulldisclosure/2025/Jun/20"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://support.yealink.com/en/portal/knowledge/show?id=6476e7cd6a27da76bd06a9c9"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://www.yealink.com/en/trust-center/security-advisories/ecb16a4993014d22"
    }
  ],
  "sourceIdentifier": "cve@mitre.org",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-295"
        }
      ],
      "source": "cve@mitre.org",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.