dbcve.org
Webboss.io CmsApplication · Webboss

CVE-2023-36339

HIGH · 7.5 CVSS v3.1 Published 2023-07-21
Fix available
A fix is available. Upgrade to 3.7.0.1 or later.
See remediation →
84/100
Remediation priority · High
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
An access control issue in WebBoss.io CMS v3.7.0.1 allows attackers to access the Website Backup Tool via a crafted GET request.

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

WebBoss.io CMS v3.7.0.1 contains a broken access control vulnerability in its Website Backup Tool. Attackers can exploit this by sending a crafted GET request to access the backup functionality without authentication, potentially allowing unauthorized download of sensitive backup data including configurations and user information.

MitigationImplement proper authentication and role-based authorization checks on the Website Backup Tool endpoint to ensure only authenticated users with appropriate privileges can access it; verify the vendor patch (v3.7.0.2 or later) is applied.

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
Webboss.io CmsApplication
Affected:< 3.7.0.1

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
None
Availability
None

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

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

  1. Identify WebBoss.io CMS version
    Check the admin panel footer, version info in system settings, or look for version markers in the application's main config file or database
    Affected if Installed version is less than 3.7.0.1 (or cannot be determined but falls within that range)
  2. Locate the Website Backup Tool configuration
    Access the admin dashboard and navigate to the Website Backup Tool section, or inspect the application's configuration files for backup-related settings and module enablement status
    Affected if The Website Backup Tool module or feature is enabled in the system
  3. Verify backup endpoint accessibility
    Send a crafted GET request to the suspected backup endpoint path (commonly /backup, /admin/backup, or /tools/backup based on typical WebBoss.io URL patterns) without providing any authentication credentials
    Affected if The request returns a valid response or backup data without requiring login credentials
  4. Check for backup file exposure
    Inspect the web server's document root or designated backup directory for publicly accessible backup archives; attempt to access common backup file naming patterns (e.g., backup.zip, site-backup.tar.gz) directly via HTTP
    Affected if Backup files are present in a web-accessible directory or downloadable without authentication

A user is affected if their WebBoss.io CMS installation is version 3.7.0.0 or earlier AND the Website Backup Tool feature is enabled AND the backup endpoint or backup files are accessible without authentication.

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 3.7.0.1 or later
Fixed in 3.7.0.1
Interim mitigation

Implement proper authentication and role-based authorization checks on the Website Backup Tool endpoint to ensure only authenticated users with appropriate privileges can access it; verify the vendor patch (v3.7.0.2 or later) is applied.

Recommended fix Moderate confidence

WebBoss.io CMS version 3.7.0.2 or later

  1. 1. Identify the current version of WebBoss.io CMS installed on your system
  2. 2. Navigate to the official WebBoss.io website or their download portal
  3. 3. Download the latest stable version of WebBoss.io CMS (version 3.7.0.2 or later)
  4. 4. Before upgrading, create a complete backup of the database and all CMS files
  5. 5. Review the upgrade documentation provided by WebBoss.io for any specific migration steps
  6. 6. Perform the upgrade following the documented procedure
  7. 7. Verify that the Website Backup Tool now requires proper authentication
  8. 8. Test that unauthorized access to the backup tool is no longer possible
Caveat Review WebBoss.io release notes for any breaking changes between your current version and 3.7.0.2

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

Fix this in Webboss.io Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

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