dbcve.org
Pt Project NotebooksWordPress extension · Ptoffice

CVE-2025-5304

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-28
Fix available
A fix is available. Upgrade to after 1.1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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 PT Project Notebooks plugin for WordPress is vulnerable to Privilege Escalation due to missing authorization in the wpnb_pto_new_users_add() function in versions 1.0.0 through 1.1.3. This makes it possible for unauthenticated attackers to elevate their privileges to that of an administrator.

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 PT Project Notebooks WordPress plugin versions 1.0.0-1.1.3 lacks authorization checks in the wpnb_pto_new_users_add() function, allowing unauthenticated attackers to create administrative user accounts and gain full control of the WordPress site.

MitigationUpdate to plugin version 1.1.4 or later which includes proper authorization checks; if unavailable, disable the plugin or remove user registration capabilities.

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
Pt Project NotebooksWordPress extension
Affected:>= 1.0.0, <= 1.1.3

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, locate 'Pt Project Notebooks' or 'Ptoffice Pt Project Notebooks', and note the installed version number
    Affected if Version displayed is between 1.0.0 and 1.1.3 inclusive
  2. Check plugin files directly
    If wp-admin access is unavailable, inspect the plugin main file (typically in wp-content/plugins/pt-project-notebooks/ or similar naming) and read the version comment/header
    Affected if Version retrieved from plugin files is between 1.0.0 and 1.1.3 inclusive
  3. Inspect for unauthorized admin accounts
    Go to WordPress admin > Users and review all accounts with Administrator role. Check creation dates and email addresses for suspicious entries (especially recent accounts with random-looking usernames or unfamiliar email domains)
    Affected if There are administrator accounts you did not create, especially with recent creation dates
  4. Check for suspicious registration activity
    Review WordPress user registration logs or server access logs for POST requests to endpoints containing 'pto_new_users_add' or similar registration functions, especially from unauthenticated IPs
    Affected if Unauthenticated requests to user registration endpoints are present in logs

You are affected if the Pt Project Notebooks plugin version is 1.0.0 through 1.1.3 and either unauthorized admin accounts exist or unauthenticated requests to the registration function are logged.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.1.3
Interim mitigation

Update to plugin version 1.1.4 or later which includes proper authorization checks; if unavailable, disable the plugin or remove user registration capabilities.

Recommended fix Moderate confidence

Version 1.1.4 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate 'PT Project Notebooks' in the plugin list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/pt-project-notebooks/ and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is functioning correctly and test user role assignments.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pt Project Notebooks Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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