Web origin policy bypass in Google Chrome prior to 152.0.7977.65 allows a remote attacker to violate the browser's same-origin isolation guarantees through a crafted Chrome extension delivered via social engineering. The CWE-459 incomplete cleanup root cause means residual state is left after a browsing or extension context transition, enabling a malicious extension to interact with origins it should not have access to - resulting in a High integrity impact per the CVSS vector. No public exploit code and no CISA KEV listing are confirmed at time of analysis; the EPSS score of 0.24% (14th percentile) reflects low observed exploitation pressure, consistent with the social-engineering prerequisite and the Chromium team's own Low severity designation.
Out-of-bounds memory read in the GPU component of Google Chrome on Android (prior to 152.0.7977.65) exposes process memory outside the renderer sandbox when a victim visits a crafted HTML page. The flaw targets Android-specific GPU code paths in Chrome's rendering pipeline, producing a high confidentiality impact limited to the GPU process memory space, with no integrity or availability consequence. No public exploit has been identified at time of analysis, and an EPSS probability of 0.24% at the 15th percentile indicates low near-term opportunistic exploitation likelihood.
Incorrect authorization in Chrome's StorageAccessAPI (versions prior to 152.0.7977.65) enables a renderer-compromised attacker to bypass the web origin policy via a crafted HTML page. This is a chained vulnerability - exploitation is contingent on a prior renderer process compromise, making it a second-stage component in a multi-bug attack chain rather than a standalone threat. No public exploit identified at time of analysis; EPSS at 0.23% (14th percentile) confirms low independent exploitation probability, consistent with Chromium's own 'Low' internal severity rating despite the NVD-assigned 6.5 CVSS score.
Missing authorization in Google Chrome's Network component prior to version 152.0.7977.65 enables remote attackers to bypass system access restrictions with high integrity impact by luring a user to a crafted HTML page. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N) confirms network-reachable exploitation requiring no attacker-side privileges, though a single user interaction gates the attack. No public exploit code or CISA KEV listing has been identified at time of analysis, and the EPSS score of 0.23% (13th percentile) reflects low observed exploitation probability despite broad product exposure.
Missing authorization in Chrome's InterestGroups API allows a renderer-compromised attacker to bypass system access restrictions via a crafted PDF file. Affected are all Google Chrome versions prior to 152.0.7977.65 across desktop platforms. This is a chained exploit: a prerequisite renderer-process compromise must already exist before the InterestGroups flaw can be leveraged to escalate beyond sandbox constraints and achieve high integrity impact. No public exploit or CISA KEV listing exists; EPSS stands at 0.23% (13th percentile), reflecting very low exploitation probability in the wild.
SQL injection in WP Project Manager Pro (WordPress plugin by weDevs, all versions through 4.0.1) allows authenticated attackers holding Subscriber-level access or higher to append arbitrary SQL clauses to existing plugin queries, enabling extraction of sensitive data from the WordPress database. The CVSS vector confirms high confidentiality impact with no integrity or availability consequences - the primary risk is database read access, potentially exposing user credentials and application data. No public exploit code or active exploitation has been identified at time of analysis, though the low privilege requirement (any registered WordPress user) meaningfully broadens the viable attacker pool.
Missing authorization in the BrowserTag component of Google Chrome prior to 152.0.7977.65 enables remote attackers to extract sensitive information by distributing a crafted Chrome extension via social engineering. The flaw bypasses authorization checks within BrowserTag, allowing the malicious extension to access data it should not be permitted to read. No active exploitation has been identified (CISA KEV absent), EPSS sits at 0.23% (13th percentile), and Chromium's own severity classification is 'Low' - all consistent with the UI:R prerequisite of tricking a user into installing a hostile extension.
Information leak in the Animation component of Google Chrome prior to 152.0.7977.65 allows remote unauthenticated attackers to obtain sensitive browser data by inducing a user to visit a crafted HTML page. The flaw is classified CWE-200 (Exposure of Sensitive Information) and carries a CVSS confidentiality impact of High, though Chromium's internal team rated it Medium severity. No public exploit or CISA KEV listing exists at time of analysis, and EPSS of 0.22% (13th percentile) confirms very low observed exploitation probability, making this a normal patch-cycle priority rather than an emergency.
DOM information leak in Google Chrome prior to 152.0.7977.65 enables remote attackers to extract sensitive browser data by inducing a victim to visit a crafted HTML page via social engineering. The vulnerability (CWE-200) reflects improper information exposure within Chrome's Document Object Model, with high confidentiality impact per CVSS. No active exploitation is confirmed (not in CISA KEV), EPSS sits at the 13th percentile (0.22%), and a vendor-released patch is available in stable channel 152.0.7977.65.
Information disclosure in Google Chrome's Autofill component on Android (prior to 152.0.7977.65) enables a remote attacker to extract sensitive user data - likely form-fill credentials or PII - by luring a victim to a specially crafted HTML page. The vulnerability stems from CWE-20 improper input validation in the Autofill subsystem, which fails to sanitize attacker-controlled HTML before processing it. No public exploit code or CISA KEV listing is present at time of analysis; EPSS sits at the 13th percentile, indicating low current exploitation momentum despite the high confidentiality impact.
SQL injection in the FluentCRM Pro WordPress plugin (all versions up to and including 3.1.12) enables authenticated attackers holding Author-level access or higher to append arbitrary SQL to existing queries and extract sensitive data from the WordPress database. Reported by Wordfence, the flaw stems from unsanitized user-supplied parameters passed into unparameterized SQL queries. No public exploit code or CISA KEV listing has been identified at time of analysis, but the high-confidentiality CVSS rating reflects meaningful exposure of subscriber lists, CRM data, and potentially credential material stored in the database.
UI misrepresentation in Google Chrome's Web Authentication (WebAuthn) subsystem - covering both Passkeys and hardware Security Keys - prior to version 152.0.7977.65 allows remote attackers to manipulate authentication dialog presentation via a crafted HTML page, enabling bypass of system access restrictions through social engineering. The CVSS vector rates Integrity impact as High (I:H) with no privileges required (PR:N), yet Chromium's own team assigned Low severity, and EPSS exploitation probability is just 0.22% (12th percentile), reflecting the social engineering dependency. No public exploit has been identified and no CISA KEV listing exists at time of analysis.
Race condition in Chrome's Extensions subsystem (versions prior to 152.0.7977.65) enables a remote attacker to bypass system access restrictions via a crafted Chrome extension, achieving high integrity impact with no confidentiality or availability effect. User interaction is required, and Chromium's own internal severity rating is Low - notably lower than the NVD CVSS Medium score of 6.5 - consistent with EPSS of 0.22% (12th percentile) and SSVC's 'none' exploitation status. No public exploit exists and the vulnerability is not in CISA KEV at time of analysis.
Incorrect authorization in Google Chrome's Media component on Windows enables a remote attacker who has already compromised the renderer process to bypass OS-level system access restrictions via a crafted HTML page. Affected are all Chrome versions prior to 152.0.7977.65 on Windows. No public exploit code has been identified and EPSS probability is very low at 0.21% (11th percentile), though the sandbox-escape nature of this flaw makes it a meaningful chaining risk in multi-stage attacks.
Incorrect authorization in Google Chrome's WebXR implementation prior to version 152.0.7977.65 enables cross-origin data exfiltration via a crafted HTML page, requiring attacker-driven social engineering to direct a victim to the malicious page. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) scores 6.5, reflecting high confidentiality impact but no integrity or availability loss, and user interaction is a necessary prerequisite. No public exploit code exists and the vulnerability is absent from the CISA KEV catalog at time of analysis, with EPSS at 0.21% (11th percentile) confirming low observed exploitation activity.
Unauthorized repository read in JFrog Artifactory's Composer repository handling exposes package metadata to authenticated users who lack explicit read permissions on the affected repository. The flaw stems from a missing authorization check (CWE-862) during Composer metadata requests, meaning repository-level access controls can be silently bypassed. No active exploitation has been confirmed and no public exploit code is known, but the confidentiality impact is rated High by JFrog, and affected deployments should upgrade to the fixed Artifactory release.
Information disclosure via Chrome's DataTransfer API in versions prior to 152.0.7977.65 allows remote attackers to obtain sensitive information when a victim visits and interacts with a crafted HTML page. Chromium's own Low severity classification creates a notable tension with the CVSS C:H rating, likely indicating that the scope of leaked data is constrained despite the high confidentiality label. No public exploit code or active exploitation has been confirmed; EPSS at 0.21% (11th percentile) places this firmly in the routine patching category.
Cross-origin information leakage in the FoldableAPIs component of Google Chrome prior to 152.0.7977.65 enables a remote attacker to read sensitive device-geometry data from foldable-form-factor devices by luring a user to a crafted HTML page. The affected API fails to enforce origin isolation, exposing data that should be inaccessible to untrusted cross-origin scripts. No public exploit has been identified and SSVC rates exploitation status as none; Chromium's own internal severity classification of 'Low' contrasts with the NVD-assigned 6.5 Medium, reflecting the bounded real-world impact.
Information disclosure in Google Chrome's Geolocation component prior to version 152.0.7977.65 allows a remote attacker to obtain the victim's sensitive geolocation data by tricking them into visiting a crafted HTML page. The attack relies on social engineering as the delivery mechanism and results in a high-confidentiality-impact leak of physical location information, which may expose home or workplace addresses. No public exploit code or active exploitation has been identified; EPSS at 0.21% (11th percentile) confirms low automated exploitation probability at time of analysis.
CSS injection in Google Chrome prior to version 152.0.7977.65 enables a remote attacker to extract sensitive information from a victim's browser session by delivering a crafted HTML page. The CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N vector confirms unauthenticated network delivery requiring only that the victim navigate to attacker-controlled content, with high confidentiality impact and no integrity or availability consequences. No public exploit has been identified at time of analysis, and the EPSS score of 0.20% at the 10th percentile indicates very low observed exploitation probability; this is not listed in the CISA KEV catalog.
Incorrect authorization in the TabGroups feature of Google Chrome prior to 152.0.7977.65 allows a remote attacker to leak sensitive browser information by serving crafted network traffic to a victim user. The flaw is classified CWE-863 (Incorrect Authorization), meaning the browser fails to properly enforce access control within tab group contexts, and was rated Medium severity by the Chromium security team. No public exploit identified at time of analysis, and an EPSS of 0.20% at the 10th percentile confirms very low observed exploitation activity.
Skia, the 2D graphics rendering library embedded in Google Chrome's renderer process, contains an uninitialized resource flaw that allows remote attackers to read stale sandbox memory contents by inducing a victim to visit a crafted HTML page. All Chrome versions prior to 152.0.7977.65 are affected across desktop platforms, with confidentiality impact confined to the renderer sandbox. The EPSS score of 0.19% (9th percentile) and absence from CISA KEV reflect low observed exploitation pressure, though such memory-read primitives are classically useful as components in multi-stage exploit chains targeting browser memory.
Memory disclosure in Google Chrome's Dawn WebGPU component exposes uninitialized memory contents to remote attackers who can lure a user to a crafted HTML page. Affected are all Chrome versions prior to 152.0.7977.65 on desktop platforms, per the EUVD and Chrome release advisory. No public exploit code has been identified and EPSS sits at 0.19% (9th percentile), indicating low current exploitation probability despite Chrome's ubiquitous deployment footprint.
Race condition in Google Chrome's Workers implementation before version 152.0.7977.65 allows a remote attacker to bypass system access restrictions, resulting in high integrity impact. Exploitation requires a victim to visit a crafted HTML page, placing this in the social-engineering-dependent threat category. No public exploit has been identified, and the EPSS score of 0.19% (9th percentile) indicates negligible observed exploitation in the wild at time of analysis.
StorageAccessAPI incorrect authorization in Google Chrome prior to 152.0.7977.65 enables a remote attacker who has already compromised the renderer process to bypass web origin policy via a crafted HTML page, achieving high-integrity impact against cross-origin resources. The flaw (CWE-863) is a post-exploitation second-stage primitive: it cannot be leveraged without a preceding renderer compromise, substantially narrowing its realistic threat scope beyond what the CVSS 6.5 score implies. No public exploit code has been identified, EPSS stands at 0.19%, Chromium's own internal severity rating is Low, and there is no CISA KEV listing at time of analysis.
Code injection in Google Chrome's Bisection component allows remote attackers to exfiltrate sensitive information by enticing a user to open a crafted file. Affected versions are all Chrome releases prior to 152.0.7977.65 across desktop platforms. The vulnerability carries a CVSS 6.5 Medium rating with high confidentiality impact; no public exploit has been identified and EPSS sits at 0.19% (8th percentile), indicating minimal active exploitation pressure at time of analysis. Vendor patch is confirmed available.
Cookie input validation bypass in Google Chrome prior to 152.0.7977.65 enables an attacker who has already compromised the renderer process to circumvent web origin policy restrictions. Exploitation requires a second-stage attack where a separately compromised renderer is leveraged via a crafted HTML page, making this a chained exploit component rather than a standalone initial-access vulnerability. No public exploit code has been identified and CISA has not listed this in the KEV catalog; EPSS at 0.18% (8th percentile) and a 'Low' Chromium-internal severity rating reflect limited real-world exploitation risk.
Web origin policy bypass in Google Chrome on Windows (prior to 152.0.7977.65) via improper input validation in the New Tab Page (NTP) Footer component enables integrity compromise without confidentiality loss. Exploitation is contingent on the attacker having already achieved renderer process compromise, making this a chained, post-exploitation primitive rather than a standalone vector. No public exploit code exists and EPSS sits at the 8th percentile, consistent with Chromium's own Low severity rating - though the integrity impact is rated High under CVSS.
Web origin policy bypass in Google Chrome's ReadingList component on Windows enables a renderer-compromised attacker to cross origin boundaries via a crafted HTML page. Affected are all Chrome for Windows versions prior to 152.0.7977.65. No public exploit code or active exploitation has been identified; EPSS sits at 0.18% (8th percentile), and Chromium's own security team rates this as Low severity despite the NVD CVSS score of 6.5.
Information disclosure in Google Chrome's Mobile component on iOS exposes sensitive data to local attackers operating via a local program, affecting all Chrome for iOS versions prior to 152.0.7977.65. The vulnerability is classified CWE-200 (Exposure of Sensitive Information) and carries a Chromium internal severity of Low, which aligns with SSVC's assessment of partial technical impact and non-automatable exploitation. No public exploit code exists and no active exploitation has been confirmed; the EPSS score of 0.18% (7th percentile) reflects minimal real-world exploitation pressure.
Sensitive information disclosure in Google Chrome on Windows prior to 152.0.7977.65 exposes confidential browser or system data to remote attackers who trick users into visiting a crafted HTML page. The root cause is improper input validation in Chrome's Network component (CWE-20), enabling a network-accessible attacker to exploit the flaw without privileges, though social engineering is required to achieve user interaction. No public exploit code or CISA KEV listing is confirmed, and the EPSS score of 0.17% (7th percentile) reflects low current exploitation probability despite the High confidentiality impact in the CVSS rating.
Information leak in Google Chrome's XR (WebXR) subsystem allows unauthenticated remote attackers to obtain sensitive browser-context information when a victim visits a crafted HTML page. All Chrome desktop versions prior to 152.0.7977.65 are affected, with the vendor classifying severity as Low internally despite a CVSS 3.1 base score of 6.5 driven by high confidentiality impact. No public exploit has been identified and EPSS exploitation probability is very low at 0.17% (7th percentile), suggesting real-world risk remains limited; however, the zero-friction delivery vector - a single malicious page visit - warrants prompt patching given Chrome's ubiquitous deployment.
Out-of-bounds read in Chrome's Skia graphics library exposes sandbox memory to attackers who have already compromised the renderer process. Exploitation requires a prior renderer compromise plus user interaction with a crafted HTML page, making this a chained second-stage information disclosure rather than a standalone critical flaw. Chromium's own severity rating is Low; no public exploit or CISA KEV listing exists, and EPSS sits at just 0.17%.
Out-of-bounds memory read in Chrome's Tint graphics library on Android exposes sandbox-contained memory to remote attackers. Google Chrome for Android prior to 152.0.7977.65 is affected; an attacker who lures a user to a crafted HTML page can trigger the flaw and read arbitrary memory within the Chrome sandbox. No active exploitation has been identified - Chromium's own security team rates this as Low severity, consistent with the 0.17% EPSS score and the absence of a CISA KEV listing.
Out-of-bounds memory read in Google Chrome's FileSystem component (versions prior to 152.0.7977.65) allows a remote unauthenticated attacker to leak memory contents from outside the browser's renderer sandbox by directing a victim to a specially crafted HTML page via social engineering. Exploitation is contingent on user interaction, limiting opportunistic or automated mass exploitation. No public exploit code exists and EPSS sits at 0.17% (7th percentile), though the Confidentiality impact is rated High, meaning successful exploitation could expose sensitive data from browser memory. Vendor-released patch is available in Chrome 152.0.7977.65.
Sensitive information exposure in Google Chrome for Android (versions prior to 152.0.7977.65) via the Android Intents mechanism allows a remote attacker to leak confidential browser or device data by delivering a crafted HTML page to the victim. The vulnerability requires user interaction - the target must visit the malicious page - limiting opportunistic mass exploitation despite the network-accessible attack vector. No public exploit code has been identified at time of analysis, and EPSS probability is low at 0.17%, consistent with Chromium's own 'Low' severity classification, though the CVSS C:H rating reflects a meaningful confidentiality impact if triggered.
CSS information leak in Google Chrome before 152.0.7977.65 enables remote attackers to exfiltrate sensitive browser data by luring victims to a crafted HTML page. The flaw resides in Chrome's CSS rendering subsystem (CWE-200: Information Exposure) and carries a CVSS C:H rating, meaning confidentiality impact is assessed as high despite the medium-severity label. No public exploit code has been identified and EPSS probability sits at 0.17% (7th percentile), indicating very low observed exploitation activity; the vulnerability is not listed in the CISA KEV catalog.
Incorrect DOM authorization in Google Chrome prior to 152.0.7977.65 enables remote unauthenticated attackers to potentially leak sensitive information by serving a crafted HTML page to a victim. The flaw is classified as CWE-863 (Incorrect Authorization), meaning Chrome's DOM implementation fails to properly enforce access controls for certain document-level resources. No public exploit code has been identified and EPSS sits at 0.17% (6th percentile), consistent with Chrome's own 'Low' severity rating despite the medium CVSS 6.5 score driven by the C:H metric.
Incorrect authorization in the Forms component of Google Chrome prior to version 152.0.7977.65 enables a remote unauthenticated attacker to obtain sensitive browser-held form data by directing a victim to a crafted HTML page. The CVSS 6.5 score reflects high confidentiality impact (C:H) with no integrity or availability consequence, consistent with a pure information disclosure primitive. No public exploit identified at time of analysis; EPSS of 0.17% at the 6th percentile and Chromium's own 'Low' internal severity rating together suggest low near-term exploitation likelihood despite the meaningful CVSS base score.
Incorrect authorization in Chrome's GetUserMedia API allows remote attackers to obtain sensitive information - specifically unauthorized access to a user's camera or microphone feed - by luring the victim to a crafted HTML page. All Chrome versions prior to 152.0.7977.65 on desktop are affected. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, but the High confidentiality impact warrants timely patching given Chrome's ubiquitous deployment.
DevTools Missing Authorization in Google Chrome prior to version 152.0.7977.65 exposes sensitive browser information to remote attackers who socially engineer victims into performing specific UI interactions. The CWE-862 root cause indicates the DevTools component lacks proper authorization checks on certain UI-driven data access paths, allowing an attacker-controlled page to extract information the browser context holds. No public exploit code has been identified and no CISA KEV listing exists; the EPSS score of 0.15% at the 5th percentile confirms minimal near-term exploitation probability despite the C:H CVSS impact rating.
The Passwords (built-in credential manager) component of Google Chrome on iOS prior to version 152.0.7977.65 leaks sensitive password data to a local attacker who can supply a crafted file, enabling unauthorized retrieval of stored credentials. Only the iOS platform is affected, and the Chromium security team rates this as Low severity internally. No public exploit code exists and EPSS stands at 0.11% (1st percentile), indicating very low near-term exploitation likelihood despite the high confidentiality impact of the exposed data.
Cross-workspace domain deletion in TypeBot prior to 3.18.0 allows any authenticated non-guest workspace member to remove custom domains belonging to other workspaces, rendering their chatbots unavailable. The `handleDeleteCustomDomain` API handler validates the caller's membership in a client-supplied workspaceId but forwards the client-supplied domain name to the shared Vercel project API without confirming that domain is owned by the authorized workspace - a classic IDOR flaw (CWE-639). No public exploit code and no CISA KEV listing exist at time of analysis, but the attack requires only valid workspace membership on the target deployment.
Stored Cross-Site Scripting in TranslatePress (WordPress plugin by cozmoslabs) versions through 3.2.6 allows authenticated attackers with subscriber-level access to inject persistent JavaScript via approved comment body content rendered in the Translation Editor's Strings Dropdown. The payload executes in the browser of any user - typically an administrator or editor - who subsequently opens the affected translation editor interface, creating a reliable subscriber-to-admin privilege escalation path through session hijacking or unauthorized administrative action. No confirmed active exploitation or public POC is identified at time of analysis; a vendor-released patch exists as version 3.3.
Stored Cross-Site Scripting in MetForm for WordPress (all versions through 4.1.8) allows authenticated contributors to permanently inject arbitrary JavaScript into pages via the 'mf_form_id' Elementor widget setting, exploiting two independent filter bypass paths. The payload evades Elementor's save-time wp_kses_post filter because it contains no HTML tags, and MetForm's own str_replace logic transforms script-tag constructs into executable JavaScript template literals - providing a second delivery route. Any visitor loading an injected page has the script execute in their browser context, enabling session hijacking or credential theft. No public exploit code or CISA KEV listing has been identified at time of analysis.
Server-side request forgery in galaxy_ng, the Ansible Galaxy server plugin for Pulp, allows authenticated users holding namespace management permissions to redirect a background worker process into probing arbitrary internal network addresses, including loopback interfaces and cloud instance metadata endpoints (e.g., 169.254.169.254). The dual-impact vulnerability enables both internal network reconnaissance (enumerating reachable IPs and reading service responses) and a denial-of-service condition against background workers due to the absence of an HTTP client timeout. No public exploit has been identified at time of analysis, and no confirmed KEV listing exists; however, the scope-changing CVSS vector (S:C) reflects that impact crosses trust boundaries from the application into adjacent internal infrastructure.
Stored XSS in the eCommerce Product Catalog WordPress plugin (≤3.5.10) by implecode allows any authenticated contributor to persist malicious JavaScript via the 'style' shortcode attribute, bypassing WordPress's save-time wp_kses_post sanitization because the payload is stored inside shortcode brackets containing no HTML tags, with dangerous markup generated only at render time by the shortcode handler. Every subsequent visitor to an injected page executes the attacker's script in their browser context, enabling session hijacking, credential theft, or malicious redirects against administrators and customers alike. No public exploit code has been identified at time of analysis and the CVE is not listed in the CISA KEV catalog, but upstream changeset 3656358 confirms a fix has been committed.
Stored Cross-Site Scripting in Ultimate Member WordPress plugin (all versions ≤ 2.12.1) allows authenticated attackers with subscriber-level access to plant persistent JavaScript via textarea profile fields with HTML support, exploiting a DOM gadget where pickadate.js concatenates stored id attribute values into the DOM via jQuery .html(). The scope change (S:C) means injected scripts execute in any visitor's browser on profile page load without additional interaction, enabling session theft, credential harvesting, or malicious redirects against administrators and regular users alike. No public exploit code has been identified at time of analysis, but the Wordfence report includes direct code-level references that materially reduce reproduction difficulty; an upstream fix commit exists.
Stored Cross-Site Scripting in the Gutenverse - WordPress Blocks, Page Builder & Site Editor plugin (all versions through 4.0.2) permits authenticated contributors to persist arbitrary JavaScript via the titleTag block attribute. The vulnerability is architecturally subtle: the malicious payload bypasses WordPress's wp_kses_post sanitization at save time by residing inside a Gutenberg block-comment delimiter, and the dangerous HTML is only synthesized when do_blocks() renders the page, at which point no further escaping is applied. Because the injected script fires in administrator and editor browser sessions during post preview, a contributor can effectively escalate impact to admin-level session hijacking. No public exploit identified at time of analysis.
Stored Cross-Site Scripting in the FundEngine WordPress plugin (versions up to and including 1.8.1) allows any authenticated user with at minimum Subscriber-level access to inject persistent malicious scripts via the `wfp_featured_video_url` parameter. The REST endpoint that processes this input has its `permission_callback` hardcoded to `__return_true`, effectively bypassing WordPress role-based access controls and exposing the vulnerable code path to the lowest-privilege registered user. Injected scripts execute in the browsers of any subsequent visitor to the affected campaign page, enabling session hijacking, credential theft, or further lateral movement. No confirmed active exploitation has been identified (not in CISA KEV) and no public exploit code is referenced at time of analysis.