This report summarizes multiple cybersecurity incidents and emerging threats including a self-rebuilding macOS ransomware named Heartbreaker, hijacked Tor exit relays capturing SSH credentials, unauthorized AI agents operating inside major US bank customer accounts, and targeted espionage by Russia's APT28 against NATO defense firms. The Heartbreaker ransomware uses a hardcoded AES key and a Rust-based self-recompilation mechanism but is currently not considered a major threat. Tor exit relays compromised by attackers intercepted SSH sessions to steal passwords and deploy malware. Several US banks have detected rogue AI agents accessing customer accounts without proper authorization. Additionally, the developer platform Railway suffered a suspected breach exposing decrypted environment variables, and PingCAP experienced data theft including source code and customer records. These incidents highlight diverse attack vectors including ransomware, supply chain compromise, espionage, and AI misuse.
baserCMS versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2 contain a stored cross-site scripting (XSS) vulnerability. This occurs because global shortcode expansion processes the entire rendered page, including HTML-escaped blog comments from unauthenticated users, allowing malicious scripts to execute in the context of site visitors or administrators. The vulnerability has been patched in versions 5.3.2 and 5.4.2.
Entire CLI hooks into Git workflows to capture AI agent sessions. Prior to version 0.7.7, a path traversal vulnerability in Entire CLI allows an attacker with push access to the checkpoints repository to craft malicious checkpoint metadata that causes entire session resume or entire checkpoint rewind to write attacker-controlled transcript data outside of the expected session directory. The issue occurs because checkpoint metadata is fetched from the remote entire/checkpoints/v1 branch and the SessionID field was used to construct filesystem paths without validation in the restore path. A malicious SessionID containing absolute paths or path traversal sequences could cause arbitrary files on the victim’s machine to be overwritten. This issue has been patched in version 0.7.7.
NetBox MCP Server versions prior to 1.2.1, when configured to use HTTP transport, lack authentication on the HTTP endpoint. This allows any client with network access to the MCP server port to establish a valid session and gain full read-only access to all four NetBox tools without requiring tokens or credentials. The vulnerability has been addressed in version 1.2.1.
baserCMS versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2 have a vulnerability in the public API endpoint for mail message submissions. The API endpoint does not enforce the form's captcha verification, allowing unauthenticated attackers to automate submissions without solving the captcha challenge. This can lead to spam in administrator inboxes, attacker-influenced auto-replies, and accumulation of mail message records in the database. The issue has been patched in versions 5.3.2 and 5.4.2.
baserCMS versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2 contain a deserialization vulnerability in the widget-area entity. This flaw allows an administrator or an attacker with widget-write capability to store malicious serialized objects via the admin JSON API. These objects are deserialized without class restrictions, enabling remote code execution as the web-server user upon unauthenticated page access after payload storage. The vulnerability has been patched in versions 5.3.2 and 5.4.2.
baserCMS is a website development framework. In versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2, an authenticated user with only theme-file view permission can traverse outside the theme directory through the optional BcThemeFile plugin's Admin web screen. ThemeFilesController::parseArgs() constructs a path containing literal ../ segments, and the view and edit actions pass it to ThemeFilesService::get() without containment validation. Authorization checks the unresolved request path, after which ThemeFile::_getContents() reads the resolved file and exposes its contents in the form textarea. A client must preserve the dot segments rather than normalize them away. Readable files are limited to .php, .css, .js, and .ctp; this can disclose application source and config/install.php database credentials in MySQL or PostgreSQL deployments, while SQLite configurations have an empty database password. Reading config/app_local.php may expose the Security.salt fallback, which is effective only when not overridden by environment configuration. The flaw does not disclose .env, .pem, or SQLite .db files, does not itself permit file writes or code execution, and does not affect the separate API getFullpath() route. The plugin is disabled by default and unauthenticated requests are not sufficient. This issue has been patched in versions 5.3.2 and 5.4.2.
baserCMS versions 5.2.3 before 5.3.2 and 5.4.0 before 5.4.2 contain a path traversal vulnerability in the optional BcThemeFile plugin's Admin API. The vulnerability arises because encoded path traversal sequences are decoded after validation, allowing an authenticated administrator to write PHP files outside the intended theme directory, such as into the webroot, and execute them. Exploitation requires an administrator session, the non-default plugin enabled, and a same-origin Origin header. The issue has been patched in versions 5.3.2 and 5.4.2.
baserCMS versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2 contain an SQL injection vulnerability in the Admin and Api/Admin prefixes. Authenticated users with admin panel access can inject SQL fragments via request query parameters passed directly to the ORM, potentially allowing arbitrary SQL execution including reading password hashes. The vulnerability was patched in versions 5.3.2 and 5.4.2.
A mailbox quota-accounting vulnerability in Zimbra Collaboration Suite (ZCS) allows an authenticated user to consume another user’s mailbox quota by repeatedly sharing and revoking a document. Creation of the recipient’s shared-file record charges the document size to mailbox-wide usage. Revocation deletes the record and reverses its folder counters without reversing the mailbox-wide charge. Repeated normal share notifications therefore accumulate quota usage after the visible records are gone. On accounts with a finite quota, this can prevent incoming mail and other size-increasing operations without recipient interaction. The issue affects ZCS 10.1.16 and 10.1.20.
An SMTP command injection vulnerability in the data-source testing functionality of Zimbra Collaboration Suite (ZCS) allows an ordinary authenticated user with account options enabled to inject CR/LF into the emailAddress inserted into an SMTP envelope command by a JSON SOAP request. After a successful preliminary POP3 or IMAP login, Zimbra sends the injected commands to the selected SMTP service. If that service accepts the pipelined transaction, the attacker can submit mail with attacker-selected recipients, headers and body content without victim interaction. The vulnerable command-construction path is present in ZCS 10.1.16 and 10.1.20.
An LDAP filter injection vulnerability in Zimbra Collaboration Suite (ZCS) allows an authenticated user to query otherwise unreturned attributes of calendar resources through SearchCalendarResourcesRequest. Zimbra escapes search values but inserts the supplied attribute names directly into LDAP filter expressions without validation. An attacker can inject additional conditions and use repeated matching queries to recover readable resource attributes such as internal mailbox hostnames and mail transport routes. The search remains restricted to calendar-resource objects and the LDAP service account's access rights. ZCS 10.1.16 and 10.1.21 are affected.
A cross-account authorization vulnerability in Zimbra Collaboration Suite (ZCS) allows an authenticated user to insert forged shared-file records into another user's mailbox through FileSharedWithMeRequest. The request bypasses delegated-account authorization and accepts attacker-selected file metadata, owner identifiers and declared sizes without validating a corresponding document share. An attacker can plant entries attributed to another real local account without that account sharing a document. No victim interaction is required. ZCS 10.1.16 and 10.1.20 are affected.
A CSS sanitization vulnerability in Zimbra Collaboration Suite (ZCS) allows an authenticated user with Briefcase access to publish a document that displays attacker-controlled content under the Zimbra origin. When processing a stylesheet containing non-ASCII characters, DefangFilter appends the final ASCII segment without sanitizing it. HTML stored as application/x-zimbra-doc can therefore retain CSS URL references that the normal sanitizer removes. An attacker can share a crafted document that loads external resources and displays a credential-collection form using Zimbra's own visual assets. Exploitation requires the victim to open the document in a browser that renders the content type inline; credential theft additionally requires form submission. ZCS 10.1.16 and 10.1.20 are affected.
A vulnerability in the GTM Server Side plugin by stape.io for WordPress allows unauthenticated attackers to access another customer's full order data, including personally identifiable information (PII), via the WooCommerce purchase event tracking mechanism. This affects versions from 2.0.0 up to but not including 2.1.48. The issue has been fixed in version 2.1.48.
baserCMS is a website development framework. Starting in version 5.0.0-beta1 and prior to versions 5.3.2 and 5.4.2, `PermissionGroupsService::build()` reads a plugin's `config/permission.php` to decide what each user group may reach. When that file is absent it writes a wildcard allow rule instead: `url` `/baser/<prefix>/<plugin>/*`, `method` `*`, `auth` true, for every non-admin group. BcCustomContent has no such file in any release. After an administrator installs it, the default `operators` group can store and execute arbitrary PHP under the document root. Versions 5.3.2 and 5.4.2 patch the issue.
baserCMS versions 5.2.5 before 5.3.2 and 5.4.0 before 5.4.2 contain an improper input validation vulnerability in public mail forms. An unauthenticated visitor can supply a comma-separated list of email addresses in the email field, causing a single auto-reply to be sent to multiple third parties. This occurs when server-side VALID_EMAIL validation is not enabled on newly created forms with email-type fields. The bundled contact form is not affected as it enables VALID_EMAIL validation by default. The issue has been fixed in versions 5.3.2 and 5.4.2.
Hidden functionality (undocumented backdoor) in the root-privileged 'assistant' daemon in DJI CrystalSky ZS600C firmware v0.3.9.7 through v0.6.6.9 on Android allows a physically-present attacker with USB access to execute arbitrary OS commands as root by sending the hard-coded magic string 'dji26656677' to the USB-gadget serial interface (/dev/ttyGS0), after which each subsequent line is passed to system().
A hostname canonicalization vulnerability in the email HTML sanitizers of Zimbra Collaboration Suite (ZCS) allows an unauthenticated sender to bypass the restriction on forms that target the Zimbra host. DefangFilter and the OWASP ActionAttributePolicy compare the form-action hostname with the request hostname before browser URL canonicalization. A percent-encoded hostname can therefore survive sanitization while the browser submits the form to the normal Zimbra origin with the recipient's authentication cookie. This permits authenticated form requests from a crafted email after the recipient opens it in Classic and submits the form. The issue is present in ZCS 10.1.16 and 10.1.21. It does not bypass an endpoint's CSRF-token checks; a state-changing attack additionally requires an endpoint that accepts the resulting request without that protection.
An organizer authentication vulnerability in Zimbra Collaboration Suite (ZCS) allows an unauthenticated email sender to insert calendar invitations attributed to another user. The email delivery path permits external invitations but does not verify that the message sender is authorized to use the iCalendar ORGANIZER identity. When automatic invitation insertion is enabled, a crafted REQUEST component creates an event containing attacker-selected meeting details and reminders under a forged organizer without recipient interaction. No corresponding event is created in the claimed organizer's calendar. ZCS 10.1.16 and 10.1.21 are affected.