dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-53291

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Missing Authorization vulnerability in spoddev2021 Spreadconnect wc-spod.This issue affects Spreadconnect: from n/a through <= 2.1.5.

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 confidence

This is a missing authorization vulnerability in the Spreadconnect plugin (wc-spod) versions through 2.1.5. The application fails to properly verify user permissions before allowing access to certain functionality or data, potentially allowing unauthorized users to perform actions or access resources they should not be able to.

MitigationImplement proper authorization checks (access control) on all sensitive functions and endpoints within the Spreadconnect plugin to verify user permissions before allowing access.

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 checks

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

  1. Check if Spreadconnect plugin is installed
    Navigate to WordPress admin > Plugins page, or inspect the wp-content/plugins/ directory for a folder named 'wc-spreadconnect' or 'wc-spod'
    Affected if The plugin folder exists in the plugins directory
  2. Determine installed plugin version
    In WordPress admin, view the plugin details page to see the version number, or open the main plugin PHP file (e.g., wc-spreadconnect.php) and check the 'Version' header in the plugin comment block
    Affected if Version is 2.1.5 or lower, or version cannot be determined (treat as affected)
  3. Verify plugin is active
    Check the WordPress Plugins admin page - look for the 'Active' status indicator next to the Spreadconnect plugin
    Affected if Plugin is installed and shows as Active
  4. Confirm the authorization vulnerability scope
    Review the plugin settings and capabilities - the vulnerability allows unauthorized access to sensitive functionality without proper permission checks; test accessing plugin endpoints or features that should require admin/manager privileges
    Affected if Non-privileged users (e.g., subscribers, customers) can access plugin admin functions or data they should not be able to see

You are affected if the Spreadconnect (wc-spod) plugin is installed, active, and the version is 2.1.5 or lower, since all versions up to 2.1.5 contain the missing authorization flaw.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks (access control) on all sensitive functions and endpoints within the Spreadconnect plugin to verify user permissions before allowing access.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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