Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell is on CISA’s exploited list. Most WordPress hosting runs PHP. See if your site is affectedFlagged by our vulnerability database: PHP2Shell is being exploited. DetailsExploited: PHP2Shell. Check your site
HuttenlocherTechnologies
Updated 27 min ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,764exploited flaws on CISA’s list
36added in the last 30 days
479new WordPress flaws this week
390,525entries in the database

71 results · page 2 of 2

  • Sep 18, 2020An issue was discovered in Gradle Enterprise 2018.5 - 2020.2.4.CVE-2020-15772 · Other software · Gradle · reported by MITREMedium 4.9

    An issue was discovered in Gradle Enterprise 2018.5 - 2020.2.4. When configuring Gradle Enterprise to integrate with a SAML identity provider, an XML metadata file can be uploaded by an administrator. The server side processing of this file dereferences XML External Entities (XXE), allowing a remote attacker with administrative access to perform server side request forgery.

    Product
    Enterprise
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 18, 2020An issue was discovered in Gradle Enterprise 2018.2 and Gradle Enterprise Build Cache Node 4.1.CVE-2020-15771 · Other software · Gradle · reported by MITREHigh 7.5

    An issue was discovered in Gradle Enterprise 2018.2 and Gradle Enterprise Build Cache Node 4.1. Cross-site transmission of cookie containing CSRF token allows remote attacker to bypass CSRF mitigation.

    Product
    Enterprise
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 18, 2020An issue was discovered in Gradle Enterprise 2018.5.CVE-2020-15770 · Other software · Gradle · reported by MITREMedium 5.5

    An issue was discovered in Gradle Enterprise 2018.5. An attacker can potentially make repeated attempts to guess a local user's password, due to lack of lock-out after excessive failed logins.

    Product
    Enterprise
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 18, 2020An issue was discovered in Gradle Enterprise 2020.2 - 2020.2.4.CVE-2020-15769 · Other software · Gradle · reported by MITREMedium 6.1

    An issue was discovered in Gradle Enterprise 2020.2 - 2020.2.4. An XSS issue exists via the request URL.

    Product
    Enterprise
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 18, 2020An issue was discovered in Gradle Enterprise 2017.3 - 2020.2.4 and Gradle Enterprise Build Cache Node 1.0 - 9.2.CVE-2020-15768 · Other software · Gradle · reported by MITREHigh 7.5

    An issue was discovered in Gradle Enterprise 2017.3 - 2020.2.4 and Gradle Enterprise Build Cache Node 1.0 - 9.2. Unrestricted HTTP header reflection in Gradle Enterprise allows remote attackers to obtain authentication cookies, if they are able to discover a separate XSS vulnerability. This potentially allows an attacker to impersonate another user. Gradle Enterprise affected application request paths:/info/headers, /cache-info/headers, /admin-info/headers, /distribution-broker-info/headers. Gradle Enterprise Build Cache Node affected application request paths:/cache-node-info/headers.

    Product
    Enterprise
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 18, 2020An issue was discovered in Gradle Enterprise before 2020.2.5.CVE-2020-15767 · Other software · Gradle · reported by MITREMedium 5.3

    An issue was discovered in Gradle Enterprise before 2020.2.5. The cookie used to convey the CSRF prevention token is not annotated with the “secure” attribute, which allows an attacker with the ability to MITM plain HTTP requests to obtain it, if the user mistakenly uses a HTTP instead of HTTPS address to access the server. This cookie value could then be used to perform CSRF.

    Product
    Enterprise
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 9, 2020To be able to analyze gradle projects, the build scripts need to be executed.CVE-2020-11986 · Websites & servers · Apache · reported by security@apache.orgCritical 9.8

    To be able to analyze gradle projects, the build scripts need to be executed. Apache NetBeans follows this pattern. This causes the code of the build script to be invoked at load time of the project. Apache NetBeans up to and including 12.0 did not request consent from the user for the analysis of the project at load time. This in turn will run potentially malicious code, from an external source, without the consent of the user.

    Product
    Netbeans
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 25, 2020An issue was discovered in the Maven Extension plugin before 1.6 for Gradle Enterprise.CVE-2020-15777 · Other software · Gradle · reported by MITREHigh 7.8

    An issue was discovered in the Maven Extension plugin before 1.6 for Gradle Enterprise. The extension uses a socket connection to send serialized Java objects. Deserialization is not restricted to an allow-list, thus allowing an attacker to achieve code execution via a malicious deserialization gadget chain. The socket is not bound exclusively to localhost. The port this socket is assigned to is randomly selected and is not intentionally exposed to the public (either by design or documentation). This could potentially be used to achieve remote code execution and local privilege escalation.

    Product
    Maven
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 30, 2020All versions of com.gradle.plugin-publish before 0.11.0 are vulnerable to Insertion of Sensitive Information into Log File.CVE-2020-7599 · Other software · Gradle · reported by report@snyk.ioMedium 6.5

    All versions of com.gradle.plugin-publish before 0.11.0 are vulnerable to Insertion of Sensitive Information into Log File. When a plugin author publishes a Gradle plugin while running Gradle with the --info log level flag, the Gradle Logger logs an AWS pre-signed URL. If this build log is publicly visible (as it is in many popular public CI systems like TravisCI) this AWS pre-signed URL would allow a malicious actor to replace a recently uploaded plugin with their own.

    Product
    Plugin Publishing
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 16, 2019The PGP signing plugin in Gradle before 6.0 relies on the SHA-1 algorithm, which might allow an attacker to replace an artifact with a different one that has thCVE-2019-16370 · Other software · Gradle · reported by MITREMedium 5.9

    The PGP signing plugin in Gradle before 6.0 relies on the SHA-1 algorithm, which might allow an attacker to replace an artifact with a different one that has the same SHA-1 message digest, a related issue to CVE-2005-4900.

    Product
    Gradle
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 14, 2019The HTTP client in Gradle before 5.6 sends authentication credentials originally destined for the configured host.CVE-2019-15052 · Other software · Gradle · reported by MITRECritical 9.8

    The HTTP client in Gradle before 5.6 sends authentication credentials originally destined for the configured host. If that host returns a 30x redirect, Gradle also sends those credentials to all subsequent hosts that the request redirects to. This is similar to CVE-2018-1000007.

    Product
    Gradle
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 3, 2019JetBrains IntelliJ IDEA projects created using the Kotlin (JS Client/JVM Server) IDE Template were resolving Gradle artifacts using an http connection, potentiaCVE-2019-10103 · Other software · Jetbrains · reported by MITREHigh 8.1

    JetBrains IntelliJ IDEA projects created using the Kotlin (JS Client/JVM Server) IDE Template were resolving Gradle artifacts using an http connection, potentially allowing an MITM attack. This issue, which was fixed in Kotlin plugin version 1.3.30, is similar to CVE-2019-10101.

    Product
    Kotlin
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 28, 2019In DiffPlug Spotless before 1.20.0 (library and Maven plugin) and before 3.20.0 (Gradle plugin), the XML parser would resolve external entities over both HTTP aCVE-2019-9843 · Other software · Diffplug · reported by MITREHigh 7.5

    In DiffPlug Spotless before 1.20.0 (library and Maven plugin) and before 3.20.0 (Gradle plugin), the XML parser would resolve external entities over both HTTP and HTTPS and didn't respect the resolveExternalEntities setting. For example, this allows disclosure of file contents to a MITM attacker if a victim performs a spotlessApply operation on an untrusted XML file.

    Product
    Gradle
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 31, 2019A cross-site request forgery vulnerability in Jenkins Artifactory Plugin 3.2.2 and earlier in ReleaseAction#doSubmit, GradleReleaseApiAction#doStaging, MavenRelCVE-2019-10324 · Websites & servers · Jenkins project · reported by jenkinsci-cert@googlegroups.comMedium 6.5

    A cross-site request forgery vulnerability in Jenkins Artifactory Plugin 3.2.2 and earlier in ReleaseAction#doSubmit, GradleReleaseApiAction#doStaging, MavenReleaseApiAction#doStaging, and UnifiedPromoteBuildAction#doSubmit allowed attackers to schedule a release build, perform release staging for Gradle and Maven projects, and promote previously staged builds, respectively.

    Product
    Jenkins Artifactory Plugin
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 22, 2019OpenAPI Tools OpenAPI Generator before 4.0.0-20190419.052012-560 uses http:// URLs in various build.gradle, build.gradle.mustache, and build.sbt files, which maCVE-2019-11405 · Other software · Openapi-generator · reported by MITREHigh 8.1

    OpenAPI Tools OpenAPI Generator before 4.0.0-20190419.052012-560 uses http:// URLs in various build.gradle, build.gradle.mustache, and build.sbt files, which may have caused insecurely resolved dependencies.

    Product
    Openapi Generator
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 22, 2019arrow-kt Arrow before 0.9.0 resolved Gradle build artifacts (for compiling and building the published JARs) over HTTP instead of HTTPS.CVE-2019-11404 · Other software · Arrow-kt · reported by MITREHigh 8.1

    arrow-kt Arrow before 0.9.0 resolved Gradle build artifacts (for compiling and building the published JARs) over HTTP instead of HTTPS. Any of these dependent artifacts could have been maliciously compromised by an MITM attack.

    Product
    Arrow
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 22, 2019In Gradle Enterprise before 2018.5.2, Build Cache Nodes would reflect the configured password back when viewing the HTML page source of the settings page.CVE-2019-11403 · Other software · Gradle · reported by MITRECritical 9.8

    In Gradle Enterprise before 2018.5.2, Build Cache Nodes would reflect the configured password back when viewing the HTML page source of the settings page.

    Product
    Build Cache Node
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 22, 2019In Gradle Enterprise before 2018.5.3, Build Cache Nodes did not store the credentials at rest in an encrypted format.CVE-2019-11402 · Other software · Gradle · reported by MITRECritical 9.8

    In Gradle Enterprise before 2018.5.3, Build Cache Nodes did not store the credentials at rest in an encrypted format.

    Product
    Enterprise
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 9, 2019Gradle versions from 1.4 to 5.3.1 use an insecure HTTP URL to download dependencies when the built-in JavaScript or CoffeeScript Gradle plugins are used.CVE-2019-11065 · Other software · Gradle · reported by MITREMedium 5.9

    Gradle versions from 1.4 to 5.3.1 use an insecure HTTP URL to download dependencies when the built-in JavaScript or CoffeeScript Gradle plugins are used. Dependency artifacts could have been maliciously compromised by a MITM attack against the ajax.googleapis.com web site.

    Product
    Gradle
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 1, 2018After the Android platform is added to Cordova the first time, or after a project is created using the build scripts, the scripts will fetch Gradle on the firstCVE-2017-3160 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 7.4

    After the Android platform is added to Cordova the first time, or after a project is created using the build scripts, the scripts will fetch Gradle on the first build. However, since the default URI is not using https, it is vulnerable to a MiTM and the Gradle executable is not safe. The severity of this issue is high due to the fact that the build scripts immediately start a build after Gradle has been fetched. Developers who are concerned about this issue should install version 6.1.2 or higher of Cordova-Android. If developers are unable to install the latest version, this vulnerability can easily be mitigated by setting the CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL environment variable to https://services.gradle.org/distributions/gradle-2.14.1-all.zip

    Product
    Apache Cordova Android
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 7, 2017ObjectSocketWrapper.java in Gradle 2.12 allows remote attackers to execute arbitrary code via a crafted serialized object.CVE-2016-6199 · Other software · Gradle · reported by MITRECritical 9.8

    ObjectSocketWrapper.java in Gradle 2.12 allows remote attackers to execute arbitrary code via a crafted serialized object.

    Product
    Gradle
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.