CVE-2025-30866
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 Giannis Kipouros Terms & Conditions Per Product terms-and-conditions-per-product allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Terms & Conditions Per Product: from n/a through <= 1.2.15.
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 confidenceThis is a missing authorization vulnerability in the WordPress plugin 'Terms & Conditions Per Product' that allows users to bypass access control checks. The plugin fails to properly validate user capabilities before allowing access to modify product terms and conditions settings, potentially allowing unauthorized users to access or alter configurations they should not have permission to 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 plugin is installed and activeIn WordPress admin, go to Plugins > Installed Plugins and look for 'Terms & Conditions Per Product' or check via WP-CLI: wp plugin list --status=active --search='terms-conditions'Affected if The plugin is installed and active in the WordPress environment
-
Identify plugin versionIn Plugins list, click on the plugin name to view details, or check the plugin main file header for 'Version:' value, or use: grep -i 'Version:' /path/to/wp-content/plugins/terms-conditions-per-product/*.phpAffected if The installed version lacks the fix for CVE-2025-30866 (any unpatched version)
-
Check plugin PHP files for missing capability checksExamine the plugin's main PHP files (especially admin/settings pages or AJAX handlers) for functions that modify terms/settings without calling current_user_can() or similar authorization checks near the beginning of those functionsAffected if Functions that modify plugin settings or product terms lack proper current_user_can() validation at the start
-
Test authorization with low-privilege accountCreate or use a subscriber-level user account, then attempt to access wp-admin/admin.php?page=terms-conditions-per-product settings or any AJAX endpoint used by the plugin, observing whether access is granted without admin privilegesAffected if Non-administrator users can access and modify plugin settings or product terms configurations
A user is affected if the 'Terms & Conditions Per Product' plugin is active AND lacks proper current_user_can() capability checks in its settings/modification functions, allowing unauthorized users to alter configurations.
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 dataThe vulnerability requires adding proper capability checks (e.g., current_user_can()) to all functions that modify plugin settings or product terms configurations, ensuring only authorized users (typically administrators) can make changes.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30866 — 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-30866 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