dbcve.org
CWE-610Weakness · CWE-610

CVE-2025-15251

MEDIUM · 5.6 CVSS v3.1 Published 2025-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable No privileges 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 detected in beecue FastBee up to 2.1. Impacted is the function getRootElement of the file springboot/fastbee-server/sip-server/src/main/java/com/fastbee/sip/handler/req/ReqAbstractHandler.java of the component SIP Message Handler. The manipulation results in xml external entity reference. It is possible to launch the attack remotely. A high complexity level is associated with this attack. The exploitability is considered difficult. The project owner replied to the issue report: "Okay, we'll handle it as soon as possible."

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

This is an XML External Entity (XXE) injection vulnerability in the SIP Message Handler component of beecue FastBee. The getRootElement function in ReqAbstractHandler.java processes SIP XML messages without properly disabling external entity resolution, allowing attackers to inject malicious XML that can access internal files, perform SSRF, or cause denial of service.

MitigationDisable external entity processing in the XML parser configuration used by the SIP Message Handler. This is typically done by setting features like 'XMLConstants.ACCESS_EXTERNAL_DTD' and 'XMLConstants.ACCESS_EXTERNAL_SCHEMA' to empty strings, or using secure XMLInputFactory configurations that disable entity resolution.

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

CVSS:3.1/AV:N/AC:H/PR:N/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 FastBee installation and version
    Locate the beecue FastBee installation directory and check for version information in manifest files, README, or version configuration files.
    Affected if FastBee is installed and the SIP Message Handler component is in use.
  2. Locate ReqAbstractHandler.java
    Search the FastBee installation for the file ReqAbstractHandler.java in the SIP Message Handler source code or decompiled classes.
    Affected if The file exists and contains the getRootElement function that processes SIP XML messages.
  3. Inspect XML parser configuration in getRootElement
    Examine the getRootElement function for XMLInputFactory or DocumentBuilder configuration. Look for whether external entity resolution has been explicitly disabled.
    Affected if The XML parser is created without disabling external entities (no ACCESS_EXTERNAL_DTD/ACCESS_EXTERNAL_SCHEMA restrictions, or no XINCLUDE or external general/parameter entity features disabled).
  4. Check if SIP message processing is enabled
    Determine if the SIP Message Handler is actively processing incoming SIP XML messages. Review application configuration or routing settings that enable SIP message handling.
    Affected if SIP message handling is enabled and receiving XML-based SIP requests.
  5. Verify XML input factory security settings
    Search the codebase for XMLInputFactory configuration. Check if feature 'SUPPORT_EXTERNAL_ENTITIES' or similar is set to false, or if entity resolver is explicitly set to null/disabled.
    Affected if External entity processing is not explicitly disabled in the XMLInputFactory used by the handler.

A user is affected if FastBee with the SIP Message Handler is installed, the getRootElement function in ReqAbstractHandler.java processes SIP XML messages, and the XML parser configuration does not explicitly disable external entity resolution.

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

Disable external entity processing in the XML parser configuration used by the SIP Message Handler. This is typically done by setting features like 'XMLConstants.ACCESS_EXTERNAL_DTD' and 'XMLConstants.ACCESS_EXTERNAL_SCHEMA' to empty strings, or using secure XMLInputFactory configurations that disable entity resolution.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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