CVE-2026-28201
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 · uneditedAn improper input validation, together with an overly permissive default CORS configuration in Open Notebook v1.8.1 allows remote attacker to trick a legitimate user to alter or delete arbitrary database entries via specially crafted malicious URL. Depending on the deployment, data exfiltration is also 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 · moderate confidenceOpen Notebook v1.8.1 suffers from improper input validation combined with an overly permissive default CORS configuration. Attackers can craft malicious URLs that, when accessed by authenticated users, allow cross-origin requests to bypass protections, enabling unauthorized alteration or deletion of database entries and potential data exfiltration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.8.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of Lfnovo Open NotebookCheck the application version through the product's about page, version endpoint, or package manager listingAffected if The version is 1.8.1, 1.8.2, or any version prior to 1.8.3
-
Locate the CORS configurationSearch the application configuration files for CORS settings, typically found in files named cors, cors.json, cors.yml, or within the main application configAffected if The CORS configuration allows all origins (wildcard *) or does not explicitly specify trusted origins
-
Verify input validation on user-supplied dataReview the application configuration or code for input validation rules, particularly for URL parameters and request bodiesAffected if Input validation is not implemented or is missing for URL parameters and request bodies
The environment is affected if the installed version is below 1.8.3 and the CORS configuration is permissive (allowing all origins) without explicit input validation on user data.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.8.3
Restrict the CORS configuration to explicitly allow only trusted origins and implement rigorous input validation on all user-supplied data, particularly URL parameters and request bodies, to prevent injection attacks.
Upgrade to Open Notebook version 1.8.3 or later
- Identify the current installed version of Open Notebook by checking the application or configuration files
- Backup the existing database and configuration files before upgrading
- Download Open Notebook version 1.8.3 or the latest stable version from the official GitHub repository
- Stop the Open Notebook service or application
- Replace the existing installation files with the new version files
- Review and update configuration files if needed, particularly CORS settings to ensure they are not overly permissive
- Start the Open Notebook service
- Verify the application is running correctly and test basic functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28201 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28201 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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