Stored cross-site scripting in the Link Library WordPress plugin before 7.9.6 allows users with Contributor-level access or higher to place script content in a link field that is later rendered inside a link-preview attribute. The preview is generated without authentication and without a published-status check, so an unapproved submission can reach any visitor who opens the preview, although the victim must interact with the crafted content. The independent assessment rates it medium severity (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N) and assigns a this_month priority, so scheduled rather than emergency remediation is appropriate; the vendor fixed it in 7.9.6, no CISA KEV active-exploitation confirmation was provided, and a public PoC reference exists but is not verified as working exploit code.
Stored cross-site scripting in the Photo Engine (Media Organizer & Lightroom) WordPress plugin before 6.5.8 allows authenticated users with author-level access or higher to save collection and gallery names containing script, which is stored unsanitised and rendered unescaped in the administrative dashboard. The injected code only executes when a privileged user, typically an administrator, later views that dashboard, so successful abuse requires a site that grants author-or-higher accounts to untrusted parties; single-admin installations face little practical exposure. A public PoC reference exists but is not verified as working exploit code, there is no confirmed active exploitation, and the vendor patch is available in 6.5.8.
SQL injection in oretnom23's php-travel-agency-system lets remote attackers manipulate the costomer_id, payment_type, amount, description, user, uploadimage, full_name, and visa_no parameters in admin/insert.php, producing high confidentiality impact and limited integrity impact while availability remains unaffected. Authentication is required per the independent assessment (PR:L), even though the vendor CVSS 4.0 vector claims PR:N; the admin/ endpoint implies valid admin credentials or a separate auth bypass are needed. Publicly available exploit code exists, but the independent assessment treats this as a moderate-priority issue that should not be over-escalated; the project has not responded to the issue report and no vendor-released patch was identified at time of analysis.
FluentCart (A New Era of eCommerce), a WordPress eCommerce plugin, before version 2.2.0 fails to verify that a stored customer address selected during checkout belongs to the requester, so unauthenticated visitors can attach another customer's saved address to an order they place and read it back - exposing postal addresses, phone numbers and company details. Only sites below 2.2.0 with an active public checkout flow and customers who have previously saved addresses are in scope; the attacker must supply or enumerate a valid stored-address identifier, and disclosed data is limited to contact/shipping details, with no payment data, credentials, or write/availability impact reported. Severity is medium (CVSS 5.3, PR:N via the provided vector), there is no CISA KEV entry, and the WPScan reference is a public PoC/advisory reference that is not verified as working exploit code; overall priority is this_month rather than emergency.
Unauthenticated denial of service in the ONVIF service of Kiloview E3 encoder firmware, where malformed or incomplete requests to certain ONVIF operations render the service unresponsive while the rest of the device continues normal operation. The service recovers automatically after a period, but the condition can be retriggered repeatedly by any party able to reach the ONVIF port over the network. No public exploit code or confirmed active exploitation is identified in the available sources; the CISA ICS advisory and vendor firmware download page are the primary references, and no public exploit was identified at time of analysis.
Kiloview E3 firmware leaves certain ONVIF informational requests unauthenticated, so a remote party that can reach the device service can retrieve device identifiers and configured user-account names with privilege levels (CVSS 5.3, CWE-306). The exposure is information disclosure that supports fingerprinting and targeted credential attacks, not direct account takeover; reachability of the ONVIF service is the practical constraint. No public exploit identified at time of analysis and no CISA KEV confirmation is provided; the vuln.today decision label is this_month.
Missing authorization checks in the Photo Engine (Media Organizer & Lightroom) WordPress plugin before 6.5.8 allow authenticated users holding the author role or higher to delete arbitrary media attachments, including files uploaded by other users and administrators. The issue is an integrity-only authorization bypass (CWE-639) on the attachment-handling action: no confidentiality exposure, no code execution and no stated availability impact beyond the deleted media. No KEV listing or confirmed active exploitation is reported in the available data, only a public PoC reference that is not verified as working exploit code, and the vulnerability is treated as a moderate, this-month priority rather than an emergency; exposure is confined to sites running the plugin with author-level or higher accounts.
Stored shortcode injection in the WP Ultimate Review WordPress plugin affects every version before 2.4.5: the public review form does not neutralise shortcode syntax in all review fields, so an unauthenticated visitor can submit a review containing arbitrary shortcodes that are then executed when that field is rendered on the site, provided user reviews and that field's display are enabled. The vendor has released 2.4.5 as the fix, and a public PoC reference exists; it is not verified as working exploit code, and there is no confirmed active exploitation (not in CISA KEV). Tracked as CVE-2026-103234 with a CVSS 3.1 base score of 4.8 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N) and an EUVD record (EUVD-2026-108009), the realistic impact is bounded by which shortcodes are registered on the target site and by whether the affected field is actually displayed to a viewer.
The WordPress plugin MB Custom Post Types & Custom Taxonomies (MetaBox) before version 2.12.3 exposes a legacy data-migration routine that can be re-triggered by an unauthenticated remote request with no capability check, allowing the plugin's custom post type and taxonomy definitions to be rolled back to their pre-2.0 state. The flaw is only reachable on sites that were originally installed at a pre-2.0 release and then upgraded, because those installations still carry the legacy migration path and the old definition data; the practical impact is that administrator changes made after the upgrade are discarded, and where an administrator had tightened a definition's visibility, that restriction is silently removed and the definition and its content become visible to anonymous visitors. Exploitation requires this upgrade history plus admin-made post-upgrade changes (reflected in CVSS AC:H), no credentials or user interaction are needed (PR:N, UI:N), and a public PoC reference exists but is not verified as working exploit code; there is no confirmed active exploitation, and the issue is tracked at low-to-moderate priority (this_month).
Path traversal in Kiloview E3 firmware allows an authenticated user of the device management interface to supply a crafted time-zone value that redirects /etc/localtime outside the intended zoneinfo directory. Exploitation requires network access plus valid credentials, is rated high complexity, and is limited to confidentiality impact; this is a medium-severity issue (CVSS 5.3) rather than a top-tier emergency. No KEV confirmation is present in the supplied intelligence, and no public exploit identified at time of analysis.
Applications using the MongoDB C# Driver (2.0.0 up to but not including 3.13.0) can be induced to write malformed BSON binary elements to the database when they parse untrusted text containing an out-of-range binary subtype value. The subtype is accepted during parsing, bypasses the library's UUID and OldBinary integrity guards, and is then narrowed to a single byte on encoding, so the persisted element misdeclares its type or length; downstream readers either error out or silently interpret the value as shorter than what was originally validated. Impact is integrity and limited availability damage from corrupted persisted data, not code execution or disclosure, and the CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N, VI:L/VA:L) and the independent 3.1 assessment agree it is unauthenticated but low-impact. No public exploit code or active exploitation is reported in the available sources, and the vendor priority is 'this_month' rather than an emergency.
Missing GC rooting in Wasmtime 47.0.0 through 48.0.3 and 49.0.0 through 49.0.1 can leave a GC reference unrooted when it is live across a `try_call`, so a callee that triggers garbage collection can leave the reference stale or dangling and corrupt the GC heap or cause incorrect execution. Exposure is limited to embedders or CLI users who compile and run attacker-supplied Wasm with GC references and exception support enabled, both of which are on by default from v47; the assessed impact is primarily availability (C:N/I:N/A:H) even though one source also tags information disclosure. No public exploit code has been identified at time of analysis, and the vendor has released fixes in 48.0.4 and 49.0.2.
A BSON length-parameter inconsistency (CWE-130) in the MongoDB C# Driver prior to 3.13.0 lets unauthenticated remote attackers inject or remove elements in database commands issued by applications that build raw or lazy BSON documents from externally supplied binary data. Because the pre-fix driver copies the attacker's mismatched length prefix onto the wire verbatim instead of validating it against the actual buffer size, the server parses the excess or truncated elements as part of the command, enabling unauthorized modification and out-of-scope disclosure of stored data bounded by the application's own database privileges. Exploitation depends on that specific application coding pattern rather than on any authentication or user-interaction barrier (PR:N, UI:N); no public exploit code or KEV listing was provided, and the fix is the vendor's 3.13.0 GA release.
Arbitrary file write on the Incus CLI host occurs when an operator runs 'incus file pull -r' against a virtual machine whose in-guest incus-agent has been replaced with a malicious build; the agent returns the same directory entry name twice, first as a symlink and then as a directory or regular file, so the client recursively creates or writes through the link it just made and lands outside the intended target directory. Affected releases are Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0, and only VM-served transfers are exposed because container transfers are handled by forkfile on the host rather than by an in-guest agent. This is a genuine but conditional integrity threat rather than a mass-exploitation emergency: the attacker must already hold root inside the guest VM (the assessed vector is PR:L) and the operator must voluntarily run a recursive pull from that specific compromised VM (UI:R), with final impact bounded by the operator's privileges on the CLI host; no public exploit has been identified at time of analysis and there is no CISA KEV entry.
Grav CMS 2.0.0 through 2.2.4 lets page authors harvest visitors' HTTP Basic authentication credentials - including administrator usernames and passwords - by rendering the request Uri object, which embeds PHP_AUTH_USER and PHP_AUTH_PW, into page content such as an inline style background image that beacons the captured values to an external host. Exploitation is precondition-heavy: the site must actually be protected by HTTP Basic auth so those PHP variables are populated, the attacker must already hold a page-author account permitted to write raw Twig/HTML page content (PR:L), and a credential-bearing victim such as an administrator must actively view the authored page (UI:P) before their browser issues the outbound request. No public exploit code was identified at time of analysis, and the vendor addressed the flaw in Grav 2.2.5; the assessed severity is moderate (CVSS 4.0: 6.9; CVSS 3.1: AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N) rather than an unauthenticated remote compromise.
CPython's tarfile.tar_filter extraction filter can be bypassed with crafted link members, allowing a malicious tar archive to redirect subsequent members and write files outside the chosen destination directory, with the impact limited to the permissions of the extracting process. Only code that explicitly calls extractall() or extract() with filter="tar" is affected; the stricter data_filter was already hardened against this class of attack by CVE-2026-7774. The source CVSS 4.0 score is 6.9 (integrity-only, unauthenticated per PR:N), vuln.today rates it this_month rather than act_now/emergency, and no public exploit code or CISA KEV listing has been identified at time of analysis.
Supply chain compromise is possible in CloudPirates Open Source Helm Charts prior to commit 271d415, where pull_request_target workflows check out attacker-controlled fork code with base-repository privileges and also write to an Actions cache that release or publish jobs later restore. An attacker able to open a pull request from a fork could exfiltrate repository secrets, tokens and deploy keys, or plant a poisoned cache entry that executes during a release, enabling publication of malicious chart artifacts. The issue is fixed by commit 271d415; there is no CISA KEV entry and no public exploit code identified at time of analysis, but the disclosed pattern mirrors the TanStack supply chain compromise and the current triage label places it at this-month priority, with the caveat that GitHub's default approval requirement for first-time fork contributors (reflected in UI:R) blunts drive-by exploitation.
Denial of service in Wasmtime: Cranelift-compiled `call_ref` callsites and the exceptional catch path of `try_table` mishandle fuel accounting, so a crafted guest can drop the fuel consumed inside a callee and reset to the pre-call remaining balance, letting it run for exponential time on linear fuel and evade timeouts and periodic yields. Exposure is gated hard by configuration - fuel metering is off by default (Config::consume_fuel or -W fuel=N on the CLI), the Cranelift backend must be used (the default unless Winch is configured, and it also covers Pulley interpreter users), and the guest must actually contain the `call_ref` or `try_table` opcode. Only Wasmtime 47.0.0 through 48.0.2 and 49.0.0 are affected; 48.0.3 and 49.0.1 contain the fix, no public exploit was identified at time of analysis, and the vendor rates this medium severity at CVSS 4.0 6.9 (CWE-400 uncontrolled resource consumption).
Authentication bypass in Traefik deployments that enforce mutual TLS can let unauthenticated remote clients reach backends protected by RequireAndVerifyClientCert when an !Host() router rule creates a TLS-options conflict and Traefik falls back to default options without certificate verification. Affected releases are before 2.11.58 and 3.7.13, and exploitation requires the non-default combination of client-certificate enforcement plus a negated Host matcher. No public exploit identified at time of analysis.
Authentication bypass in NT OneAPP allows an attacker with local access to a logged-in device to circumvent the App PIN lock via a crafted Deep Link and reach protected app resources. The flaw requires the victim to already have an active authenticated session protected only by the PIN, so it defeats the at-rest PIN barrier rather than full account authentication and is not remotely exploitable. There is no public exploit identified at time of analysis and no CISA KEV entry in the provided data; the independent assessment classifies the issue as moderate risk rather than high priority.
Host process abort in Wasmtime's wasmtime-wasi crate (WASIp3, default-supported since 46.0.0, fixed in 48.0.4 and 49.0.2) lets a guest crash the Unix host by calling set-times or set-times-at on wasi:filesystem/types.descriptor with a negative seconds value, i.e. a timestamp before the Unix epoch. Only guests that have been given a preopened directory descriptor with mutable access can reach the faulty conversion path - read-only preopens are unaffected, WASIp1/WASIp2 are not vulnerable, and Windows hosts are explicitly unaffected. Per the supplied CVSS vector the trigger is unauthenticated with no user interaction (PR:N/UI:N), and the impact is availability-only (VA:H); no public exploit code or active exploitation has been identified at time of analysis, and the vendor states there are no known workarounds.
Client-side field-level encryption (CSFLE) in the MongoDB .NET/C# driver silently writes fields that should have been encrypted as plaintext when the process runs under certain platform text-encoding configurations, because an internal name conversion loses information and the operation is never matched to its configured encryption rules. Affected are driver versions from 2.10.0 up to but not including 3.13.0, and only deployments that actually have CSFLE configured and in use; an application user able to write data through such an application can cause sensitive fields to be persisted unencrypted with no error raised. There is no integrity or availability impact, no public exploit identified at time of analysis, and the issue is resolved in driver release 3.13.0.
Local users or processes on managed macOS endpoints running WatchGuard Endpoint Security with Full Disk Encryption can read the FileVault Personal Recovery Key from a world-readable diagnostic log, exposing full-disk-encryption recovery material. Exploitation requires only an existing local foothold and no privileges or user interaction; endpoints not enrolled in the FDE feature are unaffected. No public exploit code or CISA KEV entry was identified at time of analysis.
Denial of service via unbounded host memory allocation affects Wasmtime 46.0.0 through 46.0.2 and 47.0.0 through 47.0.3 when a malicious guest writes to WASIp3 file or HTTP streams; the host copies and buffers the entire guest-specified length, limited only by guest linear memory, so host availability can be exhausted. The issue is fixed in 46.0.3 and 47.0.4, and the independent assessment scores it availability-only with PR:L and AT:P/UI:P because the host must expose those streams and run untrusted guests. No public exploit identified at time of analysis, and the vuln.today priority label is this_month.
Wasmtime's wasmtime-wasi-http crate fails to enforce the wasi:io/streams check-write allowance for WASIp2 outgoing HTTP bodies, so a malicious guest module can write buffers far larger than the advertised ~1M chunk allowance and have the host keep those allocations for the lifetime of the guest's store, exhausting host memory. Hosts that embed wasmtime-wasi-http and expose the wasi:http interface to untrusted guests and that run Wasmtime before 36.0.16, 37.0.0 through 48.0.2, or 49.0.0 are affected; impact is limited to availability, with no confidentiality or integrity effect. Vendor-released patches exist in 36.0.16, 48.0.3 and 49.0.1, and no public exploit has been identified at time of analysis.
Guest WASI programs running under Wasmtime can crash the host runtime by supplying a filesystem timestamp whose sub-second field overflows into the seconds field, driving the Rust `std::time::Duration::new` construction into a panic and taking down the host process (denial of service only, with no confidentiality or integrity impact). Affected are wasmtime-wasi releases before 36.0.16, 37.0.0 through 48.0.3, and 49.0.0; the flaw is reachable only when the embedder actually runs untrusted guest code and has granted it WASI filesystem access reachable by the time-setting calls, so hosts executing only trusted first-party modules or withholding set-times capability are not realistically exposed. No active exploitation is confirmed (not in CISA KEV) and no public exploit has been identified at time of analysis; the vendor has released fixes in 36.0.16, 48.0.3, and 49.0.1.
KNIME Business Hub releases prior to 1.18.5 leak workflow names to authenticated remote users through overly informative error messages returned by the platform's catalog functionality, but only when the attacker already knows the internal workflow identifier. Impact is confined to confidentiality - no integrity or availability effect - and there is no public exploit identified at time of analysis. The vendor states a workaround is not possible, so upgrading to 1.18.5 is the only remediation; the issue is scored by the vendor at 6.9 under CVSS v4.0, while the independent assessment places it at CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, consistent with routine, this-month patching rather than an emergency response.
Missing authorization in the EverShop customer address API lets remote requests without credentials (PR:N) perform POST, PATCH and DELETE operations against /api/customers/:customer_id/addresses, so saved shipping addresses belonging to other customers can be added, modified or deleted. Only EverShop releases from 1.2.2 up to but not including 2.2.1 are affected, and exploitation is not opportunistic: the attacker must already know a valid customer_id plus the target address UUID, which are random rather than sequential and therefore not feasible to guess, making this a targeted IDOR-style attack that depends on prior knowledge or leakage of those identifiers. Impact is limited to address-record integrity and availability, with no confidentiality read path described in the available sources; no public exploit code has been identified at time of analysis and the flaw is not in CISA KEV, while the vendor has released a fix in v2.2.1.
Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 can misresolve an authenticated alias login to a user account on a different IMAP host in multi-host installations, exposing another mailbox's confidentiality and integrity. The flaw requires an authenticated login using an alias address that collides with an identity record on another IMAP host, so single-host deployments and installations without cross-host alias collisions are not affected. No public exploit has been identified at time of analysis, and the vendor has released fixed versions 1.6.20 and 1.7.5.
Password changes in Roundcube Webmail can be applied to the wrong mailbox when the password plugin uses the Modoboa driver, affecting releases before 1.6.20 and 1.7.x before 1.7.5. An authenticated Roundcube user can trigger this over the network, but exploitation is conditional on the Modoboa API account search returning another account first, so it is opportunistic rather than reliable. No public exploit was identified at time of analysis; vendor patches are available in 1.6.20 and 1.7.5.
Authlib's default RFC 7523 JWT bearer grant, in all releases prior to 1.9.0, fails to bind an incoming JWT assertion to the authorization server that receives it, because JWTBearerGrant.get_audiences() returns an empty list and verify_claims() therefore only checks that an aud claim is present rather than that it matches the server's token endpoint. An attacker who already holds a legitimately issued assertion for a different audience (obtained as a low-privilege principal) can replay it against a second authorization server that uses the default grant and shares the same JWT signing key, and receive an access token across that trust boundary. Exploitation requires all three conditions to hold - default grant without a get_audiences() override, shared signing key material, and a valid assertion for some other audience - so implementations that override get_audiences() with their own audience identifiers are explicitly not affected; the issue is not listed in CISA KEV and no in-the-wild exploitation is reported, although the vendor advisory includes a proof-of-concept script that demonstrates the bypass against Authlib's own Flask test fixtures.
HPE networking devices are affected by a moderate-severity flaw (CVSS 6.8) that an attacker on an adjacent network can trigger only after obtaining high administrative privileges; no user interaction is required and attack complexity is low. The supplied score indicates high confidentiality, integrity, and availability impact, although the source tag labels the issue as information disclosure and the affected versions and triggering feature are not identified in the available data. No public exploit identified at time of analysis.
Physical access to certain HPE networking devices can be used to read sensitive data and to alter or disrupt the device, with high confidentiality, integrity, and availability impact once an attacker has hands-on access. The CVSS 3.1 score is 6.8 (AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H): no credentials or user interaction are required, but the physical-access prerequisite sharply limits exposure to unattended, field-deployed, or physically insecure hardware. The HPE advisory hpesbnw05162en_us is the only reference supplied; no public exploit was identified at time of analysis, and the specific hardware interface or feature abused is not described in the available sources.
Ghidra releases before 12.2 extract extension ZIP archives without any cap on entry count, so a crafted archive containing a very large number of files can exhaust the local filesystem's inode pool and cause project writes, index flushes, and other host processes to fail. The flaw is availability-only: no confidentiality or integrity impact is assessed, and no credentials are needed, but an attacker must first persuade a victim to install the malicious archive through Ghidra's extension installer (local access plus user interaction). No public exploit code has been identified at time of analysis, and the aggregated signals place this at a 'this_month' priority rather than an emergency; the vendor-released patch is Ghidra 12.2.
Disk-space exhaustion in Ghidra 10.3 through 12.1 lets a crafted theme ZIP fill the host filesystem through the theme importer's icon extraction path. When a user is persuaded to import the archive, icon entries in the image/ subdirectory are written to ~/.config/ghidra/Ghidra*/images without any cap on decompressed size or compression ratio, so a small archive can expand until the partition is full, after which theme imports and other disk-writing applications fail. The flaw is availability-only - no code execution, privilege gain, or data disclosure - and there is no public exploit identified at time of analysis; exploitation requires local interaction with the import feature and user interaction, giving it a medium-severity, this-month remediation priority rather than emergency status.
Inode and disk-space exhaustion in Ghidra 10.3 through 12.1 allows an attacker who can convince a user to import a crafted theme ZIP archive to fill the host filesystem, causing Ghidra's own theme imports and other disk-dependent operations to fail. The flaw sits in ThemeReader.readZipTheme(), which extracts every entry under the archive's image/ directory into ~/.config/ghidra/Ghidra*/images without counting entries or bounding total size; an archive containing a very large number of tiny icon files drains the inode pool. The trigger is local and gated on user interaction (the victim must actively import the untrusted theme), so there is no remote or unauthenticated path, and the impact depends heavily on the target filesystem's free inodes and disk space. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the upstream fix commit caps extracted icon entries at 3000 and Ghidra 12.2 ships that cap.
Heap exhaustion in Ghidra's GZF packed-database import path can crash the JVM when a user or automated headless pipeline opens a crafted DB file whose BinaryField length is set to an arbitrarily large value. The issue is local and requires the victim to import the file; impact is availability-only (OutOfMemoryError, aborted import, and loss of unsaved work), and the supplied data records no public exploit at time of analysis. Version scope is conflicting across sources: the GHSA lists vulnerable versions below 12.2 with the fix in 12.2, while the NVD description and independent assessment refer to Ghidra through 12.2.
Disk-space exhaustion in NSA's Ghidra reverse-engineering suite affects every release before 12.2: the extension installer extracts attacker-supplied ZIP archives into ~/.config/ghidra/Ghidra*/Extensions without any cap on decompressed entry size, per-file size or compression ratio, so a small crafted 'zip bomb' extension can fill the host partition and cause later Ghidra writes and other applications' writes to fail. Exploitation is local and requires the victim to be persuaded to install the malicious archive through File > Install Extensions (the CVSS 4.0 vector is AV:L/AC:L/PR:N/UI:P with availability-only impact), and no public exploit code has been identified at the time of analysis - the practical risk is a social-engineering-driven denial of service rather than remote compromise. A vendor-released patch in Ghidra 12.2 adds a secure extractor that enforces a 100 MB per-entry limit, a 1 GB total limit and a 100:1 decompression ratio threshold.
Java heap exhaustion in Ghidra before 12.2 allows a crafted TAR or ZIP archive with an excessive number of entries to freeze the application when a user opens or batch-imports it. The archive mount code stores every entry through FileSystemIndexHelper without an entry-count limit, so a relatively small file with a huge entry count can block the UI thread and degrade the host until the process is forcibly terminated. Exploitation requires local file delivery and user interaction; no public exploit was identified at time of analysis, and the vendor has fixed the issue in Ghidra 12.2 by enforcing a 500,000-entry cap.
NT OneAPP stores account usernames and passwords in cleartext within Android backup data, so an attacker with local device access can extract credentials after initiating an ADB backup and obtaining the user's on-device confirmation. The issue is tracked as CWE-312 and rated 6.7 under CVSS 4.0, but the chain requires local access, reachable ADB/USB debugging, and explicit user approval, keeping real-world risk low to moderate. No public exploit was identified at time of analysis.
Anyone able to read crawlseo's backing Postgres database before version 0.2.5 can pull every registered user's Google access and refresh tokens in plaintext from the User.googleTokens column, then use the long-lived refresh tokens to retain indefinite access to those users' Google Search Console data. Version 0.2.5 closes the exposure by encrypting Google tokens at rest with the same key used for API keys (NEXTAUTH_SECRET or AUTH_SECRET). The weakness is a post-compromise confidentiality issue (CWE-312) that presupposes database-level access rather than a remotely triggerable flaw in the running app; no public exploit has been identified at time of analysis.
CPU and memory exhaustion in fpdf2 2.5.0 through 2.8.7 lets remote attackers who can submit SVG data to FPDF.image() stall or crash PDF generation workers with a sub-1 KB payload. Nested SVG <use> references are expanded by deep-copying the entire referenced graphics tree at every level, so a handful of groups that each re-reference the previous group produces exponential object growth; the advisory's reproduction (an 895-byte SVG) pinned a process for roughly 14 seconds under a 128 MB address-space limit before raising MemoryError. No public exploit tooling or active exploitation has been reported and the priority label is this_month, but a public proof-of-concept reproduction is included in the advisory; ResourceAccessPolicy does not mitigate it because all references are inline, and the issue is fixed in 2.8.8.
Arbitrary file deletion in ACF Extended through 0.9.2.7 allows a low-privileged authenticated user to use path traversal sequences to remove files outside the intended directory on a WordPress host, affecting integrity and availability without direct confidentiality loss. The flaw is a CWE-22 path traversal reported by Patchstack and rated CVSS 6.5; the vuln.today decision framework places it in the 'this_month' remediation queue rather than emergency action. No public exploit code or active exploitation is identified at time of analysis, and the specific vulnerable endpoint and trigger are not described in the supplied sources.
UI redressing and interface spoofing in Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 allow a remote unauthenticated attacker to deliver an HTML email whose CSS escapes the message-body scope and restyles application chrome. The victim must open the malicious message, and the realized impact is limited to visual deception rather than code execution, data theft, or privilege change. Vendor-released patches are available in 1.6.20 and 1.7.5; no public exploit was identified at time of analysis.
An authorization bypass in the OCO-Server Self-Service Portal (all releases prior to 1.2.3 with the feature enabled) lets an authenticated low-privileged portal user queue a software-uninstall job against computers and packages for which their role holds only read visibility and no deploy permission. The uninstall handler's permission-check loop never removes rejected assignment IDs before passing the original list to CoreLogic::uninstall(), and that CoreLogic instance is built with a null SystemUser so every internal checkPermission() call returns true unconditionally - the sibling install path fails closed and is not exploitable. Impact is integrity-only (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, 6.5): a portal account can disrupt installed software on machines belonging to other users or departments by enumerating sequential computer_package.id values, provided it can already read the target resources. No CISA KEV listing or active-exploitation reporting is associated with this CVE, and vulnerability-priority scoring places it in the this_month band; a detailed public PoC reproduction accompanies the upstream advisory; it is not verified as working exploit code.
Authentication bypass in the Drupal contrib module Email Verification / SMS Verification / OTP Verification (versions 0.0.0 through below 2.4.0) allows remote, unauthenticated attackers to skip the verification step the module is meant to enforce, with CVSS 3.1 scored 6.5 (AV:N/AC:L/PR:N/UI:N, C:L/I:L/A:N). Only Drupal sites that actually install and enable this contrib module - and rely on it as an access or action gate - are exposed, and the realistic impact is bounded to bypassing that check rather than full site compromise. No public exploit has been identified at time of analysis, CISA KEV does not list the issue, SSVC rates exploitation as none with partial technical impact, and EPSS is 0.19% (8th percentile), so the available decision signals converge on a this-month, non-emergency remediation priority. A vendor patch is available.
Open redirect in the Drupal Central Authentication System (CAS) Server contrib module lets remote, unauthenticated attackers craft CAS URLs that send victims to an untrusted site, which can be used to fake the source of data and support phishing. Affected deployments are the 0.x-2.0.x branch before 2.0.4 and the 2.1.x branch from 2.1.0 through 2.1.2; the reporter scored it 6.5, but exploitation depends on a victim following the crafted URL. No public exploit was identified at time of analysis, EPSS is 0.18% (7th percentile), and vendor patches are available in 2.0.4 and 2.1.3.
An authentication bypass in the contributed Drupal module 'REST & JSON API Authentication' (versions 0.0.0 through 3.2.0) allows remote attackers to reach REST/JSON API functionality that should be gated behind the module's authentication, with low confidentiality and integrity impact and no availability impact. Only Drupal sites that have deliberately installed and enabled this optional contrib module - and exposed its API endpoints over the network - are in scope; Drupal core and sites without the module are unaffected. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N for a base score of 6.5, EPSS is 0.18% (7th percentile) and there is no CISA KEV listing, so this is a moderate-priority item; no public exploit code has been identified at time of analysis. A vendor fix is available per the Drupal advisory, and the item is prioritized as 'this_month'.
Missing authorization in the Drupal Smart Content contrib module (affected range 0.0.0 through the 3.2.1 boundary) lets an unauthenticated remote attacker perform forceful browsing to reach a restricted resource, with low confidentiality and integrity impact and no availability effect. The flaw is CWE-862, and the specific endpoint, feature, or route involved is not described in the available sources. No public exploit identified at time of analysis and there is no CISA KEV entry; the vendor has released a patch and the priority signal is this_month (moderate, not urgent).
SQL injection (CWE-89, base CVSS 6.5) in the amazee.ai Private AI Provider Drupal contrib module lets an attacker inject into SQL statements executed by the module's database layer, with high confidentiality impact and limited integrity impact in the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N). Every site running the module in versions 0.0.0 through 1.3.7, or 1.4.0 through 1.4.3, is affected; exposure is bounded because this is a contrib module that most Drupal installations do not deploy. No confirmed active exploitation (not in CISA KEV) and no public exploit code were identified at time of analysis, and EPSS is low at 0.17% (6th percentile), but the vendor has published a security advisory and a patched release, and the standard Drupal contrib upgrade path applies. Note the published CVE vector scores PR:N while the independent assessment scores PR:L, so the privilege level an attacker needs is not consistently confirmed across sources.