CVE-2026-27400
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 · uneditedUnauthenticated Arbitrary File Deletion in BookPro <= 1.1.0 versions.
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 confidenceBookPro versions 1.1.0 and below contain an unauthenticated arbitrary file deletion vulnerability, allowing remote attackers to delete any file on the server file system without authentication credentials due to missing authorization checks on the file deletion functionality.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 BookPro versionCheck the application's version information, typically found in the application metadata (e.g., version file, about page, or API endpoint returning version data). Compare this to the affected range: version 1.1.0 or below.Affected if The installed version is 1.1.0 or lower.
-
Locate the file deletion endpointInspect the application's routing configuration, API routes, or web.xml (if Java-based) to identify endpoints that handle file deletion operations. Look for paths related to file removal, deletion, or unlink operations.Affected if A file deletion endpoint exists and is accessible.
-
Verify if the deletion endpoint requires authenticationAttempt to access the identified file deletion endpoint without providing any credentials (token, session, or login). Check the endpoint's authentication middleware or security configuration to confirm whether an auth check is enforced.Affected if The file deletion endpoint can be accessed and executes without requiring any authentication credentials.
-
Confirm authorization controls on file operationsReview the code or configuration for the file deletion functionality to determine if an authorization check validates user permissions before allowing file deletion. Look for role-based access control (RBAC) or ownership verification logic.Affected if No authorization check exists to verify the user has permission to delete the specific file being requested.
A user is affected if their BookPro installation is version 1.1.0 or below AND the file deletion functionality is exposed without requiring authentication and authorization.
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.
From vendor dataUpdate to a patched version of BookPro if available; otherwise, disable the file deletion functionality or implement proper authentication and authorization controls on all file operation endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27400 — 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-27400 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