dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1314

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
The 3D FlipBook – PDF Embedder, PDF Flipbook Viewer, Flipbook Image Gallery plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the send_post_pages_json() function in all versions up to, and including, 1.16.17. This makes it possible for unauthenticated attackers to retrieve flipbook page metadata for draft, private and password-protected flipbooks.

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

The 3D FlipBook WordPress plugin has a missing capability check in the send_post_pages_json() function, allowing unauthenticated attackers to retrieve flipbook page metadata for draft, private, and password-protected flipbooks. This is an Insecure Direct Object Reference (IDOR) vulnerability where the function directly accesses and returns sensitive post data without verifying user permissions.

MitigationUpdate the plugin to version 1.16.18 or later which implements proper capability checks. Until the patch is applied, consider disabling the plugin or restricting access to the vulnerable endpoint via web server configuration.

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
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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 if 3D FlipBook plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named '3d-flipbook-dflip-lite' or similar, or run 'wp plugin list' via WP-CLI to list installed plugins
    Affected if The 3D FlipBook plugin is present in the WordPress installation
  2. Determine the installed plugin version
    Open the main plugin file (usually within the plugin folder, often named 'dflip.php' or '3d-flipbook.php') and locate the version header, or check via WP-CLI: 'wp plugin get 3d-flipbook-dflip-lite --format=table'
    Affected if The version is lower than 1.16.18 (vulnerable versions)
  3. Check for existing flipbook posts with protected status
    Query the database or use WP-CLI: 'wp post list --post_type=flipbook --post_status=draft,private,publish --format=table' to see flipbook posts, or check in WordPress admin under the flipbook post type for any drafts, private, or password-protected entries
    Affected if There are flipbooks with draft, private, or password-protected status that could be exposed
  4. Verify the vulnerable AJAX endpoint is accessible
    Test if the endpoint /wp-admin/admin-ajax.php?action=dflip_post_pages_json is reachable without authentication by sending a request with a post ID parameter (e.g., ?action=dflip_post_pages_json&post_id=1)
    Affected if The endpoint responds without requiring authentication or capability verification (vulnerable configuration)
  5. Inspect the send_post_pages_json function for capability check
    Examine the plugin source code in the file containing send_post_pages_json() function (typically in includes/ or assets/js/ related files) and verify if current_user_can() or a permission check exists before returning post data
    Affected if No capability check (like current_user_can()) is present before accessing and returning flipbook post metadata

A user is affected if the 3D FlipBook plugin version is below 1.16.18 and there are draft, private, or password-protected flipbooks accessible without authentication via the vulnerable endpoint.

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

Update the plugin to version 1.16.18 or later which implements proper capability checks. Until the patch is applied, consider disabling the plugin or restricting access to the vulnerable endpoint via web server configuration.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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