CVE-2025-30767
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 · uneditedMissing Authorization vulnerability in add-ons.org PDF for WPForms pdf-for-wpforms allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PDF for WPForms: from n/a through <= 5.3.0.
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 confidenceA missing authorization vulnerability in the PDF for WPForms plugin allows unauthenticated or low-privilege attackers to access sensitive PDF generation functionality due to incorrectly configured access control security levels. The plugin fails to properly verify user permissions before allowing access to PDF-related operations.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm PDF for WPForms plugin is installedNavigate to WordPress Admin > Plugins and look for 'PDF for WPForms' in the installed plugins listAffected if The plugin is installed and active
-
Identify the installed plugin versionClick on the plugin in the WordPress plugins list to view details, or check the plugin header in /wp-content/plugins/pdf-for-wpforms/ directory for the Version commentAffected if The version is any release prior to the patched version (verify against vendor advisories)
-
Check if PDF generation endpoints are accessible without authenticationAttempt to access common PDF generation URLs associated with the plugin (such as ?action=pdf_for_wpforms_generate or similar endpoints) without logging in or using a low-privilege user accountAffected if PDF files can be generated or downloaded without being logged in or with a subscriber-level account
-
Inspect user capability requirements for PDF actionsExamine the plugin source code (likely in the main PHP file or PDF handler classes) for capability checks like 'manage_options' or 'edit_posts' before PDF operations; look for missing current_user_can() calls on PDF generation functionsAffected if No capability checks or weak capability checks (like 'read') are found on PDF generation functions
-
Verify nonce verification on PDF endpointsReview plugin code for nonce verification (check_admin_referer, wp_verify_nonce) on PDF-related form submissions and AJAX actionsAffected if Nonce verification is missing on PDF generation or processing endpoints
A user is affected if the PDF for WPForms plugin is installed and its PDF generation functionality can be accessed without proper authentication or with low-privilege user accounts due to missing capability or nonce checks.
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 the latest patched version of PDF for WPForms. If no patch is available, implement proper authorization checks (capability checks and nonce verification) on all PDF generation endpoints and restrict access to authenticated users with appropriate capabilities.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30767 — 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-2025-30767 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