Skip to content

CVE-2025-63387

Is CVE-2025-63387 real, exploitable, or a false positive? Here's the community verdict.

Community verdict: No field verdicts yet. Be the first practitioner to weigh in.

signals

public sources

Exploited in wild
Not listed
CISA KEV
Public exploit
None known
Metasploit/EDB/PoC
Base severity
7.5 High
CVSS
Exploitation prob.
30%
FIRST EPSS
Weakness
CWE-284
CWE

Moderate signals. Triage by your actual exposure and reachability.

cisa ssvc

CISA Vulnrichment · assessed

Exploitation
None
in the wild
Automatable
Yes
at scale
Technical impact
Partial
on success

CISA decision, by how critical the affected system is to you:

  • low impact → Track
  • medium impact → Track
  • high impact → Attend

Track: normal patch cycle · Track*: watch closely · Attend: patch sooner · Act: patch now. About SSVC ↗

baseline read

auto · not a community verdict

Low signal — verdict needed

Few public signals point to active risk. Whether a scanner hit here is a true or false positive depends on your version and config — community verdicts decide.

Based on CVSS · FIRST EPSS

Confirm or dispute →

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

Dify v1.9.1 is vulnerable to Insecure Permissions. An unauthenticated attacker can directly send HTTP GET requests to the /console/api/system-features endpoint without any authentication credentials or session tokens. The endpoint fails to implement proper authorization checks, allowing anonymous access to sensitive system configuration data. NOTE: The maintainer states that the endpoint is unauthenticated by design and serves as a bootstrap mechanism required for the dashboard initialization. They also state that the description inaccurately classifies the returned data as sensitive system configuration, stating that the data is non-sensitive and required for client-side rendering. No PII, credentials, or secrets are exposed.

Published

Embed this verdict
TruePositive verdict for CVE-2025-63387
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2025-63387/badge.svg)](https://www.truepositive.app/cve/CVE-2025-63387)
HTML
<a href="https://www.truepositive.app/cve/CVE-2025-63387"><img src="https://www.truepositive.app/cve/CVE-2025-63387/badge.svg" alt="TruePositive verdict for CVE-2025-63387"></a>

Live badge that updates automatically as the community verdict changes.

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: A curated baseline from public sources, shown separately from community verdicts.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    No confirmed in-the-wild exploitation or public exploit was found for this yet. FIRST EPSS estimates about a 30% chance of exploitation in the next 30 days, which is high relative to most CVEs. It is reachable over the network with no authentication and no user interaction, which is the most dangerous profile.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Same weakness: CWE-284.