CVE-2026-25368
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 codepeople Calculated Fields Form calculated-fields-form allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Calculated Fields Form: from n/a through <= 5.4.4.1.
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 confidenceThe Calculated Fields Form WordPress plugin (versions up to 5.4.4.1) contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This authorization bypass could permit authenticated users to access functionality or data they should not have permission to view or modify.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installation and versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins, locate 'Calculated Fields Form' and note the version number displayed. Alternatively, inspect the main plugin file header in wp-content/plugins/calculated-fields-form/ for the 'Version' tag.Affected if The installed version is 5.4.4.1 or any earlier version (versions 'up to' 5.4.4.1 are affected).
-
Identify plugin directory nameCheck the wp-content/plugins/ directory for a folder named 'calculated-fields-form' or similar variant containing 'calculated' in the name.Affected if The plugin directory exists, confirming the plugin is installed.
-
Locate AJAX action handlersSearch the plugin directory for PHP files containing 'add_action' calls with 'wp_ajax_' or 'wp_ajax_nopriv_' prefixes to identify AJAX endpoints. Inspect these handlers for missing capability checks (such as 'current_user_can', 'check_admin_referer', or 'wp_verify_nonce').Affected if AJAX handlers are found without proper authorization validation (missing capability or nonce checks before executing sensitive operations).
-
Review access control configurationIn the WordPress admin, navigate to the plugin settings panel (usually under 'Calculated Fields Form' menu). Look for access control, security level, or permission-related settings that control which user roles can access plugin features.Affected if The plugin exposes settings that allow configuring access control security levels, indicating the vulnerable configuration surface exists.
A user is affected if they have the Calculated Fields Form plugin installed with version 5.4.4.1 or lower and the plugin exposes AJAX endpoints or settings that lack proper authorization validation.
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 dataImplement proper capability checks and authorization validation on all sensitive functions and AJAX endpoints within the plugin. Ensure all actions verify user permissions before executing, and update to the latest patched version when available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25368 — 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-25368 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