dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-38690

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in Avirtum iPanorama 360 WordPress Virtual Tour Builder allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects iPanorama 360 WordPress Virtual Tour Builder: from n/a through 1.8.3.

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

Missing authorization vulnerability in the iPanorama 360 WordPress plugin allows unauthenticated users to access functionality that should be restricted by access control lists (ACLs). This broken access control issue in versions through 1.8.3 permits users to perform actions or access resources without proper capability checks, likely affecting administrative or sensitive functions within the plugin.

MitigationUpdate to a patched version of iPanorama 360 Virtual Tour Builder that includes proper capability checks (e.g., current_user_can()) and nonce verification on all sensitive endpoints. If no update is available, restrict access to affected endpoints via web server configuration or implement interim access controls.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 if iPanorama 360 plugin is installed
    Check the WordPress plugins directory for the iPanorama 360 plugin folder. Common path: wp-content/plugins/. Look for folders named 'ipanorama-360-virtual-tour-builder' or similar.
    Affected if The plugin folder exists in the WordPress plugins directory.
  2. Determine installed plugin version
    Open the main plugin file (typically ipanorama-360.php or similar in the plugin folder) and locate the Version header in the plugin comment block at the top of the file. Alternatively, check readme.txt for the 'Stable tag' or 'Version' entry.
    Affected if The installed version is 1.8.3 or any version prior to it (e.g., 1.8.2, 1.8.1, 1.0.0, etc.).
  3. Verify access control is missing on sensitive endpoints
    Review the plugin PHP source code for admin action handlers (functions hooked to admin_init, wp_ajax_, or wp_ajax_nopriv_). Search for actions that modify plugin settings, tour data, or user content. Check if these handlers include current_user_can() capability checks before executing sensitive operations.
    Affected if Sensitive admin functions are found without current_user_can() checks or with capability checks that can be bypassed by unauthenticated users.
  4. Test for unauthenticated access to admin functions
    Send a direct POST/GET request to common plugin AJAX endpoints (wp-admin/admin-ajax.php?action=ipanorama_...) or direct PHP files in the plugin directory without providing authentication cookies or valid nonces. Inspect the response for successful execution versus access denied errors.
    Affected if The plugin responds with successful data modification or administrative actions when accessed without authentication.

The environment is affected if the iPanorama 360 plugin version 1.8.3 or earlier is installed AND unauthenticated access to admin/sensitive functions is possible due to missing capability checks.

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

Update to a patched version of iPanorama 360 Virtual Tour Builder that includes proper capability checks (e.g., current_user_can()) and nonce verification on all sensitive endpoints. If no update is available, restrict access to affected endpoints via web server configuration or implement interim access controls.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

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