The WP Duplicate – WordPress Migration Plugin plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.1.11. This is due to a missing capability check and missing nonce check on the start_zip_creation, start_zip_download, local_sync_get_init_root_files, and local_sync_get_files_by_key AJAX actions in the start_zip_creation_dev() and sibling functions. This makes it possible for authenticated attackers, with subscriber-level access and above, to overwrite the plugin's prod_site_url setting so it points at an attacker-controlled host and enumerate arbitrary server directories, which when combined with a subsequent administrator-triggered sync results in an unsigned attacker-supplied ZIP archive being fetched, extracted via a WordPress-independent bridge deployed under the web root, resulting in remote code execution on the affected site.
The WP Duplicate – WordPress Migration Plugin plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.1.11 via the save_single_batch_file function. This is due to a PHP type-juggling authentication bypass via loose != comparison with no is_string() guard, combined with unsanitized base64-decoded path construction in save_single_batch_file() lacking any directory traversal containment. This makes it possible for authenticated attackers, with custom-level access and above, to execute code on the server. Exploitation requires that the site owner has completed the plugin's initial setup so that the site_type and prod_key_random_id options are non-empty, though any non-empty secret value is bypassable via the type-juggling flaw.
The WP Duplicate – WordPress Migration Plugin plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.1.11 via the 'file_name' parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. The authentication bypass requires submitting the JSON boolean `true` as the `prod_key_random_id` value, which coerces against any non-empty stored secret so that the loose `!=` comparison evaluates to false, skipping the rejection branch entirely without knowledge of the secret.
The AIKTP plugin for WordPress is vulnerable to Authorization Bypass via Predictable Token in all versions up to, and including, 5.0.7. The vulnerability exists because the plugin's sync token (`aiktpz_token`) is generated using PHP's non-cryptographic `uniqid()` function — producing a wall-clock-derived value with approximately one million microsecond candidates per uncertain generation second — while the unauthenticated, unthrottled REST endpoint `/wp-json/aiktp/checkToken` (registered with `permission_callback => __return_true`) acts as a public brute-force oracle for the token; simultaneously, the capability checks in `check_valid_token` and its wrappers (`verify_aiktp_token_with_edit_capability`, `verify_aiktp_token_with_upload_capability`) inspect only a server-side stored Administrator account (option `aiktp_author`) rather than the actual REST caller, meaning possession of the token alone grants Administrator-equivalent authority to any external request. This makes it possible for unauthenticated attackers to recover the sync token and then invoke `POST /wp-json/aiktp/createpost` to publish arbitrary posts attributed to a site Administrator, `POST /wp-json/aiktp/doUpdatePostWithImageURL` to overwrite the body content of any existing post, and `POST /wp-json/aiktp/doUploadImageToWP` to import remote media and attach it as the featured image of any post. Additionally, when the `aiktpz_token` option has never been initialized, the `checkToken` oracle returns success for an empty token submission due to a loose comparison in `check_valid_token`, providing a zero-effort bypass that requires no brute-forcing whatsoever.
The built-in regular expression name finder for latitude and longitude coordinates uses a pattern that is vulnerable to excessive backtracking. An attacker who can supply text that an application analyzes with this name finder can cause high CPU consumption, leading to denial of service. Users are recommended to upgrade to version 2.5.13 or 3.0.0, which fix the issue.
Vulnerability involving the exposure of sensitive information in the URLs of the UOC Virtual Campus’s document upload feature. After completing a document upload, the application includes identifiers related to the active session—such as `apjsessionid`—and other internal parameters associated with requests and users in the HTTP GET request parameters. This data may be stored in the browser history and in server or proxy logs, or transmitted via the HTTP Referer header, depending on the configuration and browsing flow. Its inclusion in the URL could allow for the unauthorized disclosure of information to third parties with access to those logs or recipients.
A flaw was found in OpenSCAP. This vulnerability allows for information disclosure when performing offline scans of untrusted filesystem images, such as container images or virtual machine (VM) disks. Because the scanner does not properly restrict symbolic link (symlink) resolution to the target image's root directory, an attacker can supply a crafted image containing links pointing to files on the host system. When the scan runs, typically with elevated privileges, OpenSCAP follows these links to read sensitive host files and expose their contents in the scan report or manipulate compliance results.
A cross-site scripting vulnerability exists in Win Bird JYUGYO SHIEN browser extensions for Google Chrome and Microsoft Edge, which allows an attacker to execute arbitrary script in the user's web browser.
In Eclipse iceoryx-rs, versions 0.0.11 to 0.0.13 and 0.1.0 as well as on the latest main branch.
`SampleReceiver::<T>::take()` and `Sample::<T>::deref()` are safe functions that hand the caller a `&T` pointing at a chunk written by another iceoryx process, but the subscriber path neither requires `T: ShmSend` nor verifies that the received chunk is at least `size_of::<T>()` bytes / `align_of::<T>()`-aligned. A peer process that publishes an undersized chunk, or any chunk at all when the subscriber chose a pointer-bearing `T`, drives a `#![forbid(unsafe_code)]` subscriber into out-of-bounds reads of adjacent shared-memory chunks or dereference of a publisher-controlled pointer.
Resolution:
It will not be fixed since this is a known limitation in iceoryx as it is the users responsibility to specify the same data type on sender and receiver side.
[iceoryx2](https://github.com/eclipse-iceoryx/iceoryx2) is the successor of iceoryx-rs where the API is designed to prevent this by default.
It is strongly recommended to migrate to iceoryx2 which is actively maintained and receives security support.
The iceoryx-rs package has officially reached End-of-life and will not receive any features, bugfixes or security fixes.
CVE-2026-133117 is a vulnerability in WebToffee WooCommerce Product Feeds before version 2.4.4. It involves the use of a hard-coded cryptographic key that allows unauthenticated attackers to bypass URL-cron signature verification. This enables attackers to send forged requests to trigger product feed generation repeatedly, leading to CPU and database resource exhaustion and overwriting of the feed file.
CVE-2026-110337 is a vulnerability in the Grafana Strava Datasource plugin versions 1.2.0 through 1.7.2. The plugin's resource handler forwards a client-supplied endpoint string and query parameters to the Strava API without validating the endpoint path. This allows any user with Viewer permissions, who have the datasources:query permission by default, to make read-only GET requests to any Strava API path permitted by the connected account's OAuth token. The plugin frontend only requires a fixed set of five endpoint patterns, but the lack of validation allows broader access. A fix restricting allowed endpoints to these five patterns is pending release.
StepSecurity, a supply chain security startup, has raised $20 million in Series A funding to accelerate the development and distribution of its security platform. The platform aims to secure multiple stages of the software development lifecycle, including developer machines, repositories, package registries, and CI/CD pipelines. The company offers a free community tier used by over 20,000 open source projects to help block compromised packages. This funding will support growth in engineering and security research teams and expand go-to-market efforts. There is no indication of a specific vulnerability or active threat associated with this announcement.
Two critical vulnerabilities in Apache software are actively exploited in attacks. CVE-2026-90436 affects Apache Axis 1.x, allowing unauthenticated remote code execution via unsafe reflection. Exploitation has been observed targeting Atlassian Confluence Data Center and N-central products. Apache does not plan to patch Axis 1.x but recommends migration or applying a published patch. CVE-2026-129448 affects Apache Roller versions 4.0.0 through 6.1.4, enabling unauthenticated remote code execution via unsafe deserialization in the XML-RPC interface. This vulnerability is actively exploited and fixed in Roller 6.1.6 and later.
CVE-2026-133109 is a low-severity vulnerability in JetBrains TeamCity before versions 2026.2.2 and 2026.1.6. It involves improper neutralization of script-related HTML tags (CWE-80) that allows HTML injection in pipeline notification emails via user and job names. This could potentially lead to limited impact such as low integrity issues but does not affect confidentiality or availability.
CVE-2026-133108 is a vulnerability in JetBrains TeamCity versions before 2026.2.2 where the current request details debug endpoint exposed authentication headers and session cookies. This exposure could lead to sensitive information leakage. The issue is fixed in version 2026.2.2. The CVSS score is low (2.7) indicating limited impact.