Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor account on target WordPress
-
DeliveryCraft request with malicious include parameter
-
ExploitTrigger local file inclusion in plugin
-
ExecutionDisclose wp-config.php / secrets
-
ImpactLeverage credentials for deeper compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V5 - File Handling File inclusion prevention, allowlisting
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Command and Control The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated WordPress account with at least Contributor privileges (CVSS PR:L), so the site must permit Contributor-level (or higher) accounts - open registration, multi-author publishing, or compromised low-tier credentials. The attack is network-reachable with no user interaction (AV:N/UI:N) but is rated high complexity (AC:H), implying the attacker must satisfy non-trivial conditions such as crafting a specific parameter value or meeting timing/path requirements rather than a single trivial request. The principal limiting factors are the Contributor authentication gate and the AC:H complexity; sites that do not grant untrusted users any authoring role are largely insulated, and the depth of impact (whether disclosure only or escalation to code execution) further depends on server-side PHP and filesystem configuration. |
| Impact | Signals are mixed and point to a real-but-gated risk rather than a mass-exploitation emergency. The CVSS vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, score 7.5) indicates network reachability with full triad impact but two meaningful brakes: high attack complexity (AC:H) and the requirement for at least Contributor privileges (PR:L), so an attacker must already hold a low-trust authenticated account on the WordPress site. There is no EPSS score, no SSVC decision data, and no KEV listing in the provided input, and no POC was referenced - meaning automation potential and in-the-wild interest are presently unquantified. The C:H/I:H/A:H impact rating from Patchstack is on the aggressive end for an LFI; confidentiality impact is well-supported (config/secret disclosure), while the high integrity/availability ratings presume LFI-to-RCE chaining that depends on server configuration and is not confirmed in the description. Net: prioritize on sites that allow untrusted Contributor registrations or multi-author setups; for tightly controlled single-author sites the practical risk is lower. |
| Exploit ScenarioDerived | An attacker registers or compromises a Contributor account on a WordPress site running Panorama Viewer <= 1.6.1, then submits a crafted request that manipulates the plugin's file-inclusion parameter to point at a sensitive local path such as wp-config.php. Despite the high attack complexity, a successful request returns or executes the targeted file, leaking database credentials and secret keys that enable deeper compromise. No public POC was referenced in the provided intelligence, so working exploitation would require attacker-developed tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 26, 2026
Local File Inclusion in the Panorama Viewer - 360 Degree Image + Video Viewer WordPress plugin (versions 1.6.1 and earlier) allows authenticated users with Contributor-level access to coerce the application into including arbitrary local files on the server. Cataloged under CWE-98 and reported by Patchstack, the flaw can expose sensitive files (e.g., wp-config.php credentials) and, depending on server conditions, escalate toward code execution. No public exploit identified at time of analysis and it is not listed in CISA KEV; the CVSS 3.1 base score is 7.5 with high attack complexity.
RemediationAI
No vendor-released patch version is identified in the available data, so confirm the latest release directly via the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/panorama/vulnerability/wordpress-panorama-viewer-360-degree-image-video-viewer-plugin-1-6-1-local-file-inclusion-vulnerability?_s_id=cve) and the WordPress plugin repository, then upgrade to any release later than 1.6.1 once published. Until a fixed version is verified, the most effective compensating control is to remove or deactivate the Panorama Viewer plugin, which eliminates the vulnerable code path at the cost of losing 360-degree viewer functionality. Because exploitation requires a Contributor account, also restrict who can hold Contributor (or higher) roles: disable open user registration or downgrade untrusted authors, accepting that legitimate multi-author workflows are curtailed. As a network-layer mitigation, deploy a WAF rule (e.g., Patchstack vPatch) to block path-traversal and file-inclusion patterns in requests to the plugin's endpoints, recognizing WAF rules can be bypassed and may cause false positives on legitimate panorama media URLs.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability lies in the PHP include/require handling of the Panorama Viewer plugin, a WordPress extension that renders 360-degree image and video panoramas. CWE-98 (Improper Control of Filename for Include/Require Statement in a PHP Program) means an attacker-influenced parameter flows into a file-inclusion call without adequate sanitization or allow-listing, letting the application load files outside the intended scope. Because the plugin executes within the WordPress/PHP runtime, an included PHP file is interpreted rather than merely read, which is why LFI in this class can read configuration secrets and, where attacker-controlled content can be staged (uploads, logs, session files), bridge toward remote code execution. Exact affected CPE strings were not provided in the NVD data; the only authoritative identifier is the plugin slug 'panorama' as referenced in the Patchstack advisory.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Contributor login needed (PR:L) and non-trivial conditions (AC:H); LFI reliably discloses secrets (C:H), but integrity/availability impact is conditional on RCE chaining, so I:L/A:L.
Primary rating from Vendor (patchstack).
CVSS VectorVendor: patchstack
DescriptionCVE.org
Contributor Local File Inclusion in Panorama Viewer - 360 Degree Image + Video Viewer <= 1.6.1 versions.
Articles & Coverage 1
Executive ViewAI
The Panorama Viewer WordPress plugin (versions ≤1.6.1) contains a local file inclusion vulnerability allowing authenticated Contributor-level users to read sensitive server files, including database credentials and configuration data, with potential escalation to code execution. Organizations using this plugin expose credential theft and server compromise risks through already-provisioned user accounts.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) restrict Contributor-level access to essential trusted users only, (2) disable plugin if not actively required, (3) implement WAF and file access controls to block arbitrary file inclusion, (4) enable file access logging to detect exploitation attempts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Local File Inclusion vulnerabilities occur when an application accepts user-controlled input to specify which file should be loaded or executed, typically through functions like PHP's `include()`, `require()`, or `fopen()`.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-39762
GHSA-3h77-4vh2-mhwg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB