CVE-2025-30932
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 WP Compress WP Compress for MainWP wp-compress-mainwp allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Compress for MainWP: from n/a through <= 6.30.32.
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 confidenceMissing authorization vulnerability in WP Compress for MainWP allows exploiting incorrectly configured access control security levels. The plugin fails to properly validate user permissions before allowing access to certain functions or data, potentially enabling unauthorized users to perform actions they should not have access to.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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.
-
Verify WP Compress for MainWP is installedCheck WordPress plugin directory for wp-compress-mainwp folder, or list active plugins via wp-cli: wp plugin list --status=active --format=csvAffected if Plugin is installed and active
-
Check installed plugin versionView plugin header in main plugin file (usually wp-compress-mainwp.php) or use wp-cli: wp plugin get wp-compress-mainwpAffected if Version falls within any affected range (compare to CVEs and advisories for this plugin)
-
Inspect WordPress user roles and capabilitiesNavigate to WordPress admin > Users > Roles and check if any custom roles were added by the plugin; use wp-cli: wp role listAffected if Custom or modified roles with elevated capabilities exist that may have been misconfigured
-
Test access to plugin admin functions with limited userCreate or use a subscriber-level user account and attempt to access wp-admin/admin.php?page=wp-compress* or any AJAX endpoints used by the pluginAffected if Lower-privileged users can access plugin admin pages or trigger actions without authorization errors
-
Check plugin settings for access control configurationExamine plugin options in wp_options table for entries like 'wp_compress_access_level' or review plugin settings page for permission-related controlsAffected if Access control settings are set to 'all users' or a permissive level rather than administrator-only
The environment is affected if WP Compress for MainWP is installed and non-administrator users can access plugin functions or data without proper authorization 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 dataImplement proper authorization checks at all access points and correct the access control security level configuration to enforce role-based permissions.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30932 — 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-30932 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