Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-87807 – Authenticated SQL Injection – SiYuan Note before v3.8.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-87807 is an authenticated SQL injection vulnerability in SiYuan Note, a self-hosted note-taking application. The flaw exists in the fullTextSearchBlock API endpoint’s method=1 parameter and allows an authenticated attacker to inject UNION SELECT statements, reading the entire blocks table and bypassing publish-access controls. All SiYuan versions prior to 3.8.2 are affected; the issue was fixed in 3.8.2.

Technical details

  • Root cause: Improper neutralization of special elements used in an SQL command (CWE-89) within the fullTextSearchBlock endpoint when handling the method=1 search parameter.
  • Trigger conditions: An authenticated user (or a user with access to a published/shared SiYuan instance) submits a crafted method=1 search query containing a UNION SELECT payload.
  • Attack vector: Network — no local access or physical interaction required; exploitation occurs over the exposed HTTP API.
  • Impact: Full read access to the blocks table, exposing document content and other sensitive data stored in the notebook database, and bypassing intended publish-access restrictions.

Affected software

  • SiYuan Note (b3log/siyuan-note) — all versions prior to 3.8.2

Severity

  • CVSS v3.1 Base Score: 7.5 (High) — Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • Also scored under CVSS v4.0 at 8.7 (High) — Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade SiYuan Note to version 3.8.2 or later, which contains the fix for this issue.
  • If patching is not immediately possible: Restrict network access to SiYuan instances (avoid direct internet exposure), disable or restrict public/anonymous access to publish/share features, and monitor logs for anomalous full-text search queries containing SQL syntax such as UNION SELECT.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Access Authorization - SiYuan, 思源笔记
  • Raw HTTP response body: exitSiYuan, b3log.org/siyuan

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge