Automattic
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in any Automattic product.
RSS Feeds for Automattic security vulnerabilities
Create a CVE RSS feed including security vulnerabilities found in Automattic products with stack.watch. Just hit watch, then grab your custom RSS feed url.
Products by Automattic Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2026 there have been 26 vulnerabilities in Automattic with an average score of 6.5 out of ten. Last year, in 2025 Automattic had 20 security vulnerabilities published. That is, 6 more vulnerabilities have already been reported in 2026 as compared to last year. However, the average CVE base score of the vulnerabilities in 2026 is greater by 1.41.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 26 | 6.52 |
| 2025 | 20 | 5.12 |
| 2024 | 25 | 6.52 |
| 2023 | 24 | 7.02 |
| 2022 | 6 | 5.72 |
| 2021 | 5 | 6.52 |
| 2020 | 1 | 6.10 |
It may take a day or so for new Automattic vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Automattic Security Vulnerabilities
| CVE | Date | Vulnerability | Products |
|---|---|---|---|
| CVE-2026-128998 | Nov 16, 2026 |
WP Job Manager 2.4.10 (WordPress) Reflected XSS via scriptrelated HTML tagsImproper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in Automattic WP Job Manager wp-job-manager allows Code Injection.This issue affects WP Job Manager: from n/a through 2.4.10. |
|
| CVE-2026-125801 | Nov 13, 2026 |
WooCommerce 11.0.011.2.2 Race Condition (Improper Sync)Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Automattic WooCommerce woocommerce allows Leveraging Race Conditions.This issue affects WooCommerce: from 11.0.0 through 11.2.2. |
|
| CVE-2026-125120 | Nov 09, 2026 |
Mongoose <6.13.11/7.8.12/8.24.3/9.9.2 countDocuments() sanitizeFilter NoSQLiMongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.11, 7.8.12, 8.24.3, and 9.9.2, Mongoose countDocuments() does not apply the configured sanitizeFilter query selector injection defense. An application that enables sanitizeFilter and passes attacker-controlled filter values to countDocuments() can therefore process query operator objects as operators rather than literal values, causing the count to include documents that should not match and potentially undermining authorization or application logic based on that count. This issue is fixed in versions 6.13.11, 7.8.12, 8.24.3, and 9.9.2. |
|
| CVE-2026-125119 | Nov 09, 2026 |
Mongoose <=6.13.12,7.8.13,8.24.7,9.11.4 sanitizeFilter config bypassMongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. From 6.0.0 until 6.13.12, 7.8.13, 8.24.7, and 9.11.4, Mongoose stores the connection-level sanitizeFilter option in Connection.config, but Query.prototype._castConditions() and query casting check other option locations and do not read that configuration. An application that enables sanitizeFilter through mongoose.connect() or createConnection() and passes an attacker-controlled object into a query filter therefore receives a connection that reports the defense as enabled while query selector objects remain unsanitized. A crafted password value using a query operator can match an account record without the expected literal password, while global configuration through mongoose.set('sanitizeFilter') and per-query Model.find().sanitizeFilter() remain unaffected. This issue is fixed in versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4. |
|
| CVE-2026-125118 | Nov 09, 2026 |
Mongoose <=6.13.12/7.8.13/8.24.7/9.11.4 ProtoPollution via Schema.virtualMongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.12, 7.8.13, 8.24.7, and 9.11.4, Schema.prototype.virtual() builds nested virtual paths without applying the special-property validation already used by Schema.path() and Schema.add(). An attacker who can influence virtual field names in dynamic schemas, content-management form builders, or schema-as-code systems can supply path segments such as __proto__, constructor, or prototype, causing the virtual-path reducer to write enumerable properties to Object.prototype or Function.prototype. The resulting prototype pollution can spoof inherited property checks such as authorization flags and can provide function-prototype gadget state to other server-side JavaScript code. This issue is fixed in versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4. |
|
| CVE-2026-125117 | Nov 09, 2026 |
Mongoose <6.13.12 / <7.8.13 / <8.24.7 / <9.11.4 Prototype Pollution via __setMongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.12, 7.8.13, 8.24.7, and 9.11.4, Mongoose can descend into inherited properties while loading database documents in init(), setting dotted paths in $__set, and merging update documents in utils.mergeClone. Attacker-controlled keys such as toString or valueOf can therefore cause Mongoose to write into shared built-in functions instead of an own property. A crafted document, Mixed path, non-strict document or subdocument, findOneAndReplace() replacement, chained update, or Query.prototype.merge() source can overwrite Object.prototype.toString.call, causing later queries on unrelated models to fail until the process restarts. Separately, when an attacker controls the dotted path passed to doc.set(path, value) for a subdocument configured with strict: false, descent through $__set can reach $__schema and alter shared validators or schema options for later documents. Mongoose already blocks __proto__, constructor, and prototype, so this issue overwrites properties on reachable shared objects rather than adding new properties directly to Object.prototype. This issue is fixed in versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4. |
|
| CVE-2026-125116 | Nov 09, 2026 |
Mongoose < 6.13.12/7.8.13/8.24.7/9.11.4 Type Confusion via Discriminator KeyMongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.12, 7.8.13, 8.24.7, and 9.11.4, Mongoose uses attacker-controlled discriminator key values, including the default __t field, to index plain-object registries such as Model.discriminators and schema.discriminators without requiring an own property. Values such as constructor, toString, or hasOwnProperty can therefore resolve to inherited built-in functions instead of a registered discriminator, causing type confusion in model construction, document creation, hydration, query and update casting, embedded discriminators, and populate operations. In the bulkWrite() insertOne path with skipValidation enabled, a constructor value can cause a raw input object to be stored without schema casting or strict filtering, and a stored poisoned document can make every query that hydrates it fail until the document is removed. The weakness reads inherited properties but does not modify Object.prototype and is not prototype pollution. This issue is fixed in versions 6.13.12, 7.8.13, 8.24.7, and 9.11.4. |
|
| CVE-2026-112329 | Oct 19, 2026 |
Sensei LMS <4.26.4 Auth Bypass in save_new_message (WordPress)The Sensei LMS WordPress plugin before 4.26.4 contains a broken access control vulnerability in the legacy save_new_message handler hooked on the init action, which validates only a generic nonce without verifying course enrollment or restricting post_id to valid post types. Authenticated attackers, including unprivileged Subscribers, can supply an arbitrary post_id for any course, lesson, or quiz to create a private message addressed to that post's author, bypassing the enrollment checks enforced by the newer REST send-message controller. |
|
| CVE-2026-112328 | Oct 19, 2026 |
Sensei LMS <4.26.4 Auth Access Bypass via add_new_module_term AJAXThe Sensei LMS WordPress plugin before 4.26.4 contains a broken access control vulnerability in the add_new_module_term AJAX handler that allows authenticated Teacher-role attackers to assign module taxonomy terms to arbitrary courses by supplying a crafted course_id, since the handler validates only a generic nonce and checks manage_options solely for slug prefixing rather than verifying course edit permissions. Attackers can reuse a nonce obtained from their own course metabox to call wp_set_object_terms against courses owned by other teachers or administrators, enabling unauthorized modification of course content they do not own. |
|
| CVE-2026-40808 | Oct 10, 2026 |
Broken Access Control in Jetpack VideoPress <= 3.6Subscriber Broken Access Control in Jetpack VideoPress <= 3.6 versions. |
|
| CVE-2026-106608 | Oct 10, 2026 |
WooCommerce 9.8.011.1.2 PrivEsc via Improper Privilege AssignmentIncorrect Privilege Assignment vulnerability in Automattic WooCommerce woocommerce allows Privilege Escalation.This issue affects WooCommerce: from 9.8.0 through 11.1.2. |
|
| CVE-2026-106601 | Oct 09, 2026 |
Jetpack <=16.2 Auth Bypass via Alternate Path (Password Recovery)Authentication Bypass Using an Alternate Path or Channel vulnerability in Automattic Jetpack jetpack allows Password Recovery Exploitation.This issue affects Jetpack: from n/a through 16.2. |
|
| CVE-2026-106602 | Oct 09, 2026 |
Jetpack <=16.2 Auth Bypass via Alternate Path in Password RecoveryAuthentication Bypass Using an Alternate Path or Channel vulnerability in Automattic Jetpack jetpack allows Password Recovery Exploitation.This issue affects Jetpack: from n/a through 16.2. |
|
| CVE-2026-66666 | Oct 06, 2026 |
WordPress <=7.1.2 Sensitive Data Leak via Sent Data (CVE-2026-66666)Insertion of Sensitive Information Into Sent Data vulnerability in Automattic WordPress allows Retrieve Embedded Sensitive Data. This issue affects WordPress: from 7.1 through 7.1.2, from 7.0 through 7.0.6, from 6.9 through 6.9.9, from 6.8 through 6.8.10, from 6.7 through 6.7.9, and from 6.6 through 6.6.9. |
|
| CVE-2026-93485 | Sep 18, 2026 |
WordPress Core <7.1.1 DOM-Based XSS VulnerabilityImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Automattic WordPress wordpress allows DOM-Based XSS.This issue affects WordPress: from n/a through 7.1. |
|
| CVE-2026-48888 | Sep 08, 2026 |
WooCommerce DoS via Unrestricted Resource Allocation (pre-11.1.0)Allocation of Resources Without Limits or Throttling vulnerability in Automattic WooCommerce allows HTTP DoS. This issue affects WooCommerce: from n/a before 11.1.0. |
|
| CVE-2026-57777 | Sep 04, 2026 |
WooCommerce <=11.0 Blind SQL Injection via Improper Neutralization of ElementsImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Automattic WooCommerce allows Blind SQL Injection. This issue affects WooCommerce: from n/a before 11.0. |
|
| CVE-2026-73562 | Aug 13, 2026 |
Prototype Pollution in Mongoose <6.13.10 via __proto__ update castingMongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.10, 7.8.10, 8.24.1, and 9.7.2, passing a user-controlled update such as MyModel.updateOne(filter, req.body) can exploit Mongoose update casting with a __proto__.x dotted path under $set. Schema.prototype.path and Schema.prototype._getPathType can treat inherited properties of schema.paths and schema.nested as schema types, allowing the casting process to set $fullPath and $parentSchemaDocArray on Object.prototype before throwing. This prototype pollution makes those properties visible on newly created objects and can cause application integrity and availability impacts. This issue is fixed in versions 6.13.10, 7.8.10, 8.24.1, and 9.7.2. |
|
| CVE-2026-42334 | May 14, 2026 |
Mongoose <6.13.9: $nor Sanitization Bypass in sanitizeFilterMongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.9, 7.8.9, 8.22.1, and 9.1.6, a vulnerability allows bypassing Mongooses sanitizeFilter query sanitization mechanism via the $nor operator. When sanitizeFilter is enabled, Mongoose wraps query operators in $eq to neutralize them. However, prior to the fix, $nor was not included in the set of logical operators that are recursively sanitized. Because $nor accepts an array (like $and and $or), and arrays do not trigger hasDollarKeys(), malicious operators such as $ne, $gt, or $regex could be injected inside a $nor clause without being sanitized. This vulnerability is fixed in 6.13.9, 7.8.9, 8.22.1, and 9.1.6. |
|
| CVE-2022-50958 | May 10, 2026 |
Jetpack WP Plugin 9.1 - Reflected XSS via post_id in grunion-form-view.phpWordPress Plugin Jetpack 9.1 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious scripts by manipulating the post_id parameter. Attackers can craft URLs to the grunion-form-view.php endpoint with script payloads in the post_id parameter to execute arbitrary JavaScript in victim browsers. |
|
| CVE-2026-39660 | Apr 08, 2026 |
Automattic WP Job Manager Missing Auth (<=2.4.1) |
|
| CVE-2026-3589 | Mar 06, 2026 |
WooCommerce 5.4.0-10.5.2: Unauth CSRF Allows Admin User CreationThe WooCommerce WordPress plugin from versions 5.4.0 to 10.5.2 does not properly handle batch requests, which could allow unauthenticated users to make a logged in admin call non store/WC REST endpoints, and create arbitrary admin users via a CSRF attack for example. |
|
| CVE-2026-22356 | Feb 20, 2026 |
Jetpack CRM <=6.7.0 LFI via Improper Filename ControlImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Automattic Jetpack CRM zero-bs-crm allows PHP Local File Inclusion.This issue affects Jetpack CRM: from n/a through <= 6.7.0. |
|
| CVE-2026-25404 | Feb 19, 2026 |
Missing Auth in WP Job Manager <=2.4 (Automattic Plugin)Missing Authorization vulnerability in Automattic WP Job Manager wp-job-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Job Manager: from n/a through <= 2.4.0. |
|
| CVE-2023-54332 | Jan 13, 2026 |
Jetpack 11.4 XSS in Contact Form via post_id enables script injectionJetpack 11.4 contains a cross-site scripting vulnerability in the contact form module that allows attackers to inject malicious scripts through the post_id parameter. Attackers can craft malicious URLs with script payloads to execute arbitrary JavaScript in victims' browsers when they interact with the contact form page. |
|
| CVE-2023-52212 | Jan 05, 2026 |
WP Job Manager <=2.0.0 CSRF Vulnerability in PluginCross-Site Request Forgery (CSRF) vulnerability in Automattic WP Job Manager allows Cross Site Request Forgery.This issue affects WP Job Manager: from n/a through 2.0.0. |
|
| CVE-2025-69015 | Dec 30, 2025 |
Missing Authorization vulnerability in Automattic Crowdsignal Forms crowdsignal-formsMissing Authorization vulnerability in Automattic Crowdsignal Forms crowdsignal-forms allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Crowdsignal Forms: from n/a through <= 1.7.2. |
|
| CVE-2025-15033 | Dec 22, 2025 |
WooCommerce 8.1-10.4.2 Order Data Leakage to Auth CustomersA vulnerability in WooCommerce 8.1 to 10.4.2 can allow logged-in customers to access order data of guest customers on sites with a certain configuration. This has been fixed in WooCommerce 10.4.3, as well as all the previously affected versions through point releases, starting from 8.1, where it has been fixed in 8.1.3. It does not affect WooCommerce 8.0 or earlier. |
|
| CVE-2023-7320 | Oct 29, 2025 |
WooCommerce <=7.8.2 Sensitive Info Exposure via Improper CORSThe WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 7.8.2, due to improper CORS handling on the Store API's REST endpoints allowing direct external access from any origin. This can allow unauthenticated attackers to extract sensitive user information including PII(Personal Identifiable Information). |
|
| CVE-2025-49042 | Oct 29, 2025 |
Stored XSS in WooCommerce (v10.0.2) Improper Input NeutralizationImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Automattic WooCommerce woocommerce allows Stored XSS.This issue affects WooCommerce: from n/a through 10.0.2. |
|
| CVE-2025-58674 | Sep 23, 2025 |
WordPress Core Stored XSS (CVE-2025-58674) up to v6.8.2Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WordPress allows Stored XSS. WordPress core security team is aware of the issue and working on a fix. This is low severity vulnerability that requires an attacker to have Author or higher user privileges to execute the attack vector.This issue affects WordPress: from 6.8 through 6.8.2, from 6.7 through 6.7.3, from 6.6 through 6.6.3, from 6.5 through 6.5.6, from 6.4 through 6.4.6, from 6.3 through 6.3.6, from 6.2 through 6.2.7, from 6.1 through 6.1.8, from 6.0 through 6.0.10, from 5.9 through 5.9.11, from 5.8 through 5.8.11, from 5.7 through 5.7.13, from 5.6 through 5.6.15, from 5.5 through 5.5.16, from 5.4 through 5.4.17, from 5.3 through 5.3.19, from 5.2 through 5.2.22, from 5.1 through 5.1.20, from 5.0 through 5.0.23, from 4.9 through 4.9.27, from 4.8 through 4.8.26, from 4.7 through 4.7.30. |
|
| CVE-2025-58246 | Sep 23, 2025 |
WP <=6.8.2: Insert Sensitive Info into Outgoing Data (Contributor Priv.)Insertion of Sensitive Information Into Sent Data vulnerability in WordPress allows Retrieve Embedded Sensitive Data. The WordPress Core security team is aware of the issue and is already working on a fix. This is a low-severity vulnerability. Contributor-level privileges required in order to exploit it. This issue affects WordPress: from 6.8 through 6.8.2, from 6.7 through 6.7.3, from 6.6 through 6.6.3, from 6.5 through 6.5.6, from 6.4 through 6.4.6, from 6.3 through 6.3.6, from 6.2 through 6.2.7, from 6.1 through 6.1.8, from 6.0 through 6.0.10, from 5.9 through 5.9.11, from 5.8 through 5.8.11, from 5.7 through 5.7.13, from 5.6 through 5.6.15, from 5.5 through 5.5.16, from 5.4 through 5.4.17, from 5.3 through 5.3.19, from 5.2 through 5.2.22, from 5.1 through 5.1.20, from 5.0 through 5.0.23, from 4.9 through 4.9.27, from 4.8 through 4.8.26, from 4.7 through 4.7.30. |
|
| CVE-2025-57924 | Sep 22, 2025 |
Automattic Developer <1.2.6 CSRF VulnerabilityCross-Site Request Forgery (CSRF) vulnerability in Automattic Developer allows Cross Site Request Forgery. This issue affects Developer: from n/a through 1.2.6. |
|
| CVE-2025-5285 | May 31, 2025 |
WooCommerce <=1.3.9 Stored XSS via htmlTag paramThe Product Subtitle for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the htmlTag parameter in all versions up to, and including, 1.3.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. |
|
| CVE-2025-5062 | May 22, 2025 |
PostMessage-Based XSS in WooCommerce <9.4.3The WooCommerce plugin for WordPress is vulnerable to PostMessage-Based Cross-Site Scripting via the 'customize-store' page in all versions up to, and including, 9.4.2 due to insufficient input sanitization and output escaping on PostMessage data. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. |
|
| CVE-2023-7168 | May 15, 2025 |
Jetpack <=8.0 XSS via Unsanitized Settings in Better Follow ButtonThe Better Follow Button for Jetpack WordPress plugin through 8.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). |
|
| CVE-2024-6584 | May 15, 2025 |
Arbitrary GET via wp_ajax_boost_proxy_ig in WordPress Boost PluginThe 'wp_ajax_boost_proxy_ig' action allows administrators to make GET requests to arbitrary URLs. |
|
| CVE-2024-8009 | May 15, 2025 |
WP Sensei LMS <4.20.0 - User Email Disclosure to TeachersThe Sensei LMS WordPress plugin before 4.20.0 disclose all users of the blog including their email address to teachers on the students page |
|
| CVE-2024-12743 | May 15, 2025 |
MailPoet WP Plugin Before 5.5.2: Stored XSS via Unsanitized SettingsThe MailPoet WordPress plugin before 5.5.2 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). |
|
| CVE-2024-10075 | May 15, 2025 |
Jetpack WP Plugin <13.8: Auth Bypass Allows Unauth Shortcode ExecThe Jetpack WordPress plugin before 13.8 does not ensure that the post created by the Contact Form is only accessible to authorised users, which could allow unauthenticated users to run arbitrary shortcodes and block. |
|
| CVE-2024-10076 | May 15, 2025 |
Jetpack WordPress Plugin XSS via regex in Site Accelerator (v<13.8, Boost<3.4.8)The Jetpack WordPress plugin before 13.8, Jetpack Boost WordPress plugin before 3.4.8 use regexes in the Site Accelerator features when switching image URLs to their CDN counterpart. Unfortunately, some of them may match patterns it shouldnt, ultimately making it possible for contributor and above users to perform Stored XSS attacks |
|
| CVE-2025-22740 | Mar 27, 2025 |
Sensei LMS v4.24.4: Missing Authorization Vulnerability (CVE-2025-22740)Missing Authorization vulnerability in Automattic Sensei LMS allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Sensei LMS: from n/a through 4.24.4. |
|
| CVE-2025-26762 | Mar 27, 2025 |
WooCommerce XSS via Improper Input Neutralization Before 9.7.0Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Automattic WooCommerce woocommerce allows Stored XSS.This issue affects WooCommerce: from n/a through <= 9.7.0. |
|
| CVE-2025-0466 | Feb 04, 2025 |
WordPress Sensei LMS REST API Info Leak (v4.24.4-)The Sensei LMS WordPress plugin before 4.24.4 does not properly protect some its REST API routes, allowing unauthenticated attackers to leak sensei_email and sensei_message Information. |
|
| CVE-2024-37241 | Jan 02, 2025 |
WP Job Manager - Resume Manager 2.1.0 CSRF VulnerabilityCross-Site Request Forgery (CSRF) vulnerability in Automattic WP Job Manager - Resume Manager wp-job-manager-resumes allows Cross Site Request Forgery.This issue affects WP Job Manager - Resume Manager: from n/a through <= 2.1.0. |
|
| CVE-2024-37242 | Jan 02, 2025 |
CVE-2024-37242: Newspack Newsletters CSRF Vulnerability before 2.13.3Cross-Site Request Forgery (CSRF) vulnerability in Automattic Newspack Newsletters newspack-newsletters allows Cross Site Request Forgery.This issue affects Newspack Newsletters: from n/a through <= 2.13.2. |
|
| CVE-2024-10858 | Dec 25, 2024 |
Jetpack WordPress Plugin DOM-XSS Vulnerability in Postmessage Origin CheckThe Jetpack WordPress plugin before 14.1 does not properly checks the postmessage origin in its 13.x versions, allowing it to be bypassed and leading to DOM-XSS. The issue only affects websites hosted on WordPress.com. |
|
| CVE-2024-43338 | Nov 19, 2024 |
Crowdsignal Dashboard 3.1.2 - CSRF in Automattic WordPress PluginCross-Site Request Forgery (CSRF) vulnerability in Automattic Crowdsignal Dashboard Polls, Surveys & more polldaddy allows Cross Site Request Forgery.This issue affects Crowdsignal Dashboard Polls, Surveys & more: from n/a through <= 3.1.3. |
|
| CVE-2024-10103 | Nov 19, 2024 |
MailPoet WordPress Plugin Stored XSS VulnerabilityIn the process of testing the MailPoet WordPress plugin before 5.3.2, a vulnerability was found that allows you to implement Stored XSS on behalf of the editor by embedding malicious script, which entails account takeover backdoor |
|
| CVE-2024-10486 | Nov 18, 2024 |
Info Disclosure: print_php_information.php in Google for WooCommerce 2.8.6The Google for WooCommerce plugin for WordPress is vulnerable to Information Disclosure in all versions up to, and including, 2.8.6. This is due to publicly accessible print_php_information.php file. This makes it possible for unauthenticated attackers to retrieve information about Webserver and PHP configuration, which can be used to aid other attacks. |
|