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 2 h 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

24 results

  • Sep 28, 2026Exam4 is affected by a local privilege escalation vulnerability in the com.extegrity.LogTool privileged helper, which communicates with the application via XPC.CVE-2026-4556 · Other software · Extegrity · reported by 41c37e40-543d-43a2-b660-2fee83ea851aHigh 7.8

    Exam4 is affected by a local privilege escalation vulnerability in the com.extegrity.LogTool privileged helper, which communicates with the application via XPC. The [ConsoleLogHelper copyConsoleIntoFileFromStartDate:] method executes a syslog command using attacker-controlled parameters without proper sanitization, enabling command injection. Successful exploitation allows a local attacker to execute arbitrary commands with root privileges through LaunchSynchronous.

    Product
    Exam4
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 24, 2026Logto is the modern, open-source auth infrastructure for SaaS and AI apps.CVE-2026-63203 · Other software · logto-io · reported by GitHubHigh 7.6

    Logto is the modern, open-source auth infrastructure for SaaS and AI apps. From 1.31.0 until 1.42.0, the Account API handlers in packages/core/src/routes/account/third-party-tokens.ts allow a caller holding a same-user access token with only the openid scope to retrieve stored social or enterprise SSO provider access tokens through GET /api/my-account/identities/{target}/access-token or GET /api/my-account/sso-identities/{connectorId}/access-token. The handlers authenticate the user but do not require the identities scope that protects neighboring identity-detail operations, bypassing the intended Account API consent boundary. Exploitation requires federated token-set storage to be enabled and the affected user to have authenticated through a supported connector. A low-trust application can use the disclosed provider token against upstream APIs within that token's granted scopes. This issue is fixed in version 1.42.0.

    Product
    logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 24, 2026Logto is the modern, open-source auth infrastructure for SaaS and AI apps.CVE-2026-56739 · Other software · logto-io · reported by GitHubHigh 8.5

    Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.43.0, Logto fetches administrator-controlled outbound destinations without validating the address used for the connection. Webhook delivery in packages/core/src/libraries/hook/utils.ts can reach special-use and cloud metadata addresses. Custom OAuth2 connectors can use an attacker-selected userInfoEndpoint and forward the OAuth access token in the Authorization header, while OIDC connectors can fetch an attacker-selected jwksUri. The affected operations require tenant administrative configuration access, but they cross the server's network boundary and can expose internal data or upstream provider credentials. This issue is fixed in version 1.43.0.

    Product
    logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 28, 2026Logto through 1.42.0 contains a server-side request forgery vulnerability in the OIDC SSO connector creation endpoint that fails to validate the issuer URL paraCVE-2026-82263 · Other software · logto-io · reported by VulnCheckHigh 8.2

    Logto through 1.42.0 contains a server-side request forgery vulnerability in the OIDC SSO connector creation endpoint that fails to validate the issuer URL parameter. Tenant administrators with Management API credentials can supply arbitrary internal URLs to trigger HTTP GET requests to private network services, with response content returned in API responses.

    Product
    logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 28, 2026Logto through 1.42.0 contains a server-side request forgery vulnerability in the POST /api/hooks/:id/test endpoint that accepts arbitrary URLs without host valiCVE-2026-82262 · Other software · logto-io · reported by VulnCheckHigh 8.2

    Logto through 1.42.0 contains a server-side request forgery vulnerability in the POST /api/hooks/:id/test endpoint that accepts arbitrary URLs without host validation. Tenant administrators with Management API tokens can make the server issue HTTP POST requests to internal URLs and retrieve response bodies from services on the private network.

    Product
    logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 19, 2026Logto is the modern, open-source auth infrastructure for SaaS and AI apps.CVE-2026-63188 · Other software · logto-io · reported by GitHubHigh 8.7

    Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 0.3.9, the Logto Tunnel npm package enabled createStaticFileProxy from packages/tunnel/src/commands/tunnel/index.ts and passed request.url from static asset requests through packages/tunnel/src/commands/tunnel/utils.ts using path.join(staticPath, request.url) and then fs.open(requestPath, "r") without URL normalization or a containment check. When --experience-path was enabled and the tunnel port was reachable, an unauthenticated requester could send a path containing ../ to createStaticFileProxy and read files outside the configured static directory that were readable by the logto-tunnel process. The service used server.listen(port), which could expose the tunnel to other hosts depending on the platform and deployment. This issue is fixed in version 0.3.9.

    Product
    logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 19, 2026Logto is the modern, open-source auth infrastructure for SaaS and AI apps.CVE-2026-63187 · Other software · logto-io · reported by GitHubMedium 6.3

    Logto is the modern, open-source auth infrastructure for SaaS and AI apps. From 1.40.1 until 1.41.0, Logto's .github/workflows/commitlint.yml directly interpolated github.event.pull_request.title into the Commitlint on PR title step's inline echo command before piping the title to npx commitlint. A pull request title containing a single quote could terminate the echo string and append arbitrary shell commands on the GitHub Actions runner. The pull_request trigger used a read-only GITHUB_TOKEN and did not expose repository secrets, but injected commands could alter or disrupt the ephemeral workflow execution. This issue is fixed in version 1.41.0.

    Product
    logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 19, 2026Logto is the modern, open-source auth infrastructure for SaaS and AI apps.CVE-2026-62317 · Other software · logto-io · reported by GitHubHigh 7.5

    Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's email subaddressing blocklist in packages/core/src/libraries/sign-in-experience/email-blocklist-policy.ts used the attacker-controlled domain from email input to construct subaddressingRegex when blockSubaddressing was enabled. The permissive emailRegEx accepted multiple at signs and regular expression metacharacters, and POST /api/experience/verification/verification-code could therefore cause catastrophic backtracking in subaddressingRegex.test(email). The resulting event-loop stall could make authentication, token issuance, SSO, and the administrative console unavailable. This issue is fixed in version 1.41.0.

    Product
    logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 12, 2026In WhatsUp Gold versions released before 2026.0.2, a privileged attacker can create a LogToFile action specifying an arbitrary file extension within the IIS webCVE-2026-65939 · Other software · Progress Software Corporation · reported by security@progress.comMedium 6.8

    In WhatsUp Gold versions released before 2026.0.2, a privileged attacker can create a LogToFile action specifying an arbitrary file extension within the IIS web root.

    Product
    WhatsUp Gold
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 23, 2026Logto performs principal lookup without normalizing email and identifier strings, enabling principal collision and unauthorized account access via case- or UnicCVE-2026-15617 · Other software · Logto · reported by cret@cert.orgCritical 9.1

    Logto performs principal lookup without normalizing email and identifier strings, enabling principal collision and unauthorized account access via case- or Unicode-different identities.

    Product
    Logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 23, 2026Logto does not enforce locally configured MFA during SSO authentication, allowing users to bypass second-factor requirements and grants unauthorized access.CVE-2026-15616 · Other software · Logto · reported by cret@cert.orgCritical 9.1

    Logto does not enforce locally configured MFA during SSO authentication, allowing users to bypass second-factor requirements and grants unauthorized access.

    Product
    Logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 23, 2026Logto omits validation of the SAML <Conditions> element, enabling attackers to strip time and audience restrictions and replay assertions indefinitely.CVE-2026-15615 · Other software · Logto · reported by cret@cert.orgHigh 7.5

    Logto omits validation of the SAML <Conditions> element, enabling attackers to strip time and audience restrictions and replay assertions indefinitely.

    Product
    Logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 23, 2026Logto silently fails to delete IdP-initiated SAML sessions, enabling session replay and reuse within the session’s validity window.CVE-2026-15614 · Other software · Logto · reported by cret@cert.orgHigh 7.5

    Logto silently fails to delete IdP-initiated SAML sessions, enabling session replay and reuse within the session’s validity window.

    Product
    Logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 23, 2026Logto bypasses OIDC nonce validation when the nonce claim is absent from the id_token, enabling replay of authentication tokens and weakening session-binding.CVE-2026-15612 · Other software · Logto · reported by cret@cert.orgCritical 9.1

    Logto bypasses OIDC nonce validation when the nonce claim is absent from the id_token, enabling replay of authentication tokens and weakening session-binding.

    Product
    Logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 23, 2026Logto allows unverified email-based SSO account linking, enabling an attacker to register an identity at a permissive IdP using a victim’s email and gain unauthCVE-2026-15611 · Other software · Logto · reported by cret@cert.orgCritical 9.1

    Logto allows unverified email-based SSO account linking, enabling an attacker to register an identity at a permissive IdP using a victim’s email and gain unauthorized access to the victim’s account.

    Product
    Logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 10, 2026Logto is the modern, open-source auth infrastructure for SaaS and AI apps.CVE-2026-55789 · Other software · logto-io · reported by GitHubHigh 8.5

    Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's self-hosted SAML application IdP built the signed SAML response and assertion by string-substituting user-controlled profile attributes such as name, email, and custom attribute-mapping values into element-text placeholders of a SAML XML template using samlify 2.10.0, which left those placeholders unescaped. An authenticated low-privilege user could place XML markup in a profile attribute so Logto signed a forged SAML attribute, such as an arbitrary role, allowing privilege escalation at relying Service Providers that authorize on SAML attributes. This issue is fixed in version 1.41.0.

    Product
    logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 10, 2026Logto is the modern, open-source auth infrastructure for SaaS and AI apps.CVE-2026-55377 · Other software · logto-io · reported by GitHubHigh 8.1

    Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's Account Center step-up check accepted any active verification record that belonged to the current user and had isVerified === true. A WebAuthn registration verification record for binding a new passkey could be created and verified with only an existing Account API bearer token, then sent in the logto-verification-id header and treated as identityVerified=true by Account Center routes, allowing MFA factor management without proving possession of an existing password, identifier, or MFA factor. This issue is fixed in version 1.41.0.

    Product
    logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 10, 2026Logto is the modern, open-source auth infrastructure for SaaS and AI apps.CVE-2026-55370 · Other software · logto-io · reported by GitHubMedium 6.4

    Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's existing TOTP verification accepted a successfully used TOTP code again while the code remained inside the RFC 6238 acceptance window because the verifier used otplib's stateless check with window = 1 and did not persist or compare the accepted TOTP time-step counter. An attacker who has the victim's first factor and captures a live TOTP value can replay that value to satisfy MFA during the same acceptance window. This issue is fixed in version 1.41.0.

    Product
    logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 10, 2026Logto is the modern, open-source auth infrastructure for SaaS and AI apps.CVE-2026-54714 · Other software · logto-io · reported by GitHubMedium 6.1

    Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, @logto/core reflected the SAML RelayState, SAMLResponse, and actionUrl into a Logto-origin auto-submit HTML form in packages/core/src/saml-application/SamlApplication/utils.ts without HTML-attribute escaping. A SAML application flow with a crafted RelayState from GET or POST /api/saml/:id/authn could inject script that runs on the Logto tenant origin after the user completes login. This issue is fixed in version 1.41.0.

    Product
    logto
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 22, 2026MISP allowed a site administrator to configure an arbitrary filesystem path for the NDJSON error log used by JsonLogTool.CVE-2026-56446 · Other software · misp · reported by 5a6e4751-2f3f-4070-9419-94fb35b644e8High 8.7

    MISP allowed a site administrator to configure an arbitrary filesystem path for the NDJSON error log used by JsonLogTool. Because log entries can include attacker-controlled content, an authenticated attacker with site administrator privileges could direct log output to a PHP file in a web-accessible directory and inject PHP code through logged data. Accessing the resulting file could lead to remote code execution with the privileges of the web server process. The fix restricts log destinations to existing directories beneath APP/tmp/logs or /var/log, requires absolute paths, rejects stream wrappers and traversal-related input, and limits filenames to .log or .ndjson extensions while disallowing executable extension segments.

    Product
    misp
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 21, 2017The ULOGTOD function in ntp.d in SNTP before 4.2.7p366 does not properly perform type conversions from a precision value to a double, which allows remote attackCVE-2015-5219 · Other software · Fedoraproject · reported by Red HatHigh 7.5

    The ULOGTOD function in ntp.d in SNTP before 4.2.7p366 does not properly perform type conversions from a precision value to a double, which allows remote attackers to cause a denial of service (infinite loop) via a crafted NTP packet.

    Product
    Fedora
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 2, 2014Products/CMFPlone/CatalogTool.py in Plone 3.3 through 4.3.2 allows remote administrators to bypass restrictions and obtain sensitive information via an unspecifCVE-2013-7061 · Other software · Plone · reported by MITREMedium 5.5

    Products/CMFPlone/CatalogTool.py in Plone 3.3 through 4.3.2 allows remote administrators to bypass restrictions and obtain sensitive information via an unspecified search API.

    Product
    Plone
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 4, 2007Format string vulnerability in the MprLogToFile::logEvent function in Mbedthis AppWeb 2.0.5-4, when the build supports logging but the configuration disables loCVE-2007-3009 · Websites & servers · Mbedthis Software · reported by MITREMedium 4.3

    Format string vulnerability in the MprLogToFile::logEvent function in Mbedthis AppWeb 2.0.5-4, when the build supports logging but the configuration disables logging, allows remote attackers to cause a denial of service (daemon crash) via format string specifiers in the HTTP scheme, as demonstrated by a "GET %n://localhost:80/" request.

    Product
    Mbedthis Appweb Http Server
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 6, 2005syslogtocern in Acme thttpd before 2.23 allows local users to write arbitrary files via a symlink attack on a temporary file.CVE-2005-3124 · Other software · Acme Labs · reported by security@debian.orgLow 2.1

    syslogtocern in Acme thttpd before 2.23 allows local users to write arbitrary files via a symlink attack on a temporary file.

    Product
    Thttpd
    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.