CVE Index中文
L4 · Septic Tank BlewData breach · Account takeover · SaaSmeetsmore-schedule-data-theft

MeetsMore confirms account intrusions and theft of scheduling data

MeetsMore reports 201 account intrusions followed by exploitation of a scheduling feature, potentially exposing up to 366,850 records. It patched the flaw November 12 and forced affected accounts to reset passwords. Its separate KARTE exposure has different data and guidance.

Disclosed
Nov 16, 2026
Public disclosure date
Severity
Septic Tank Blew
No CVE: a breach, not a bug
Splash zone
MeetsMore customers and providers with accessed accounts or potentially exposed scheduled-request records; ProOne is excluded.
Data breach · Account takeover · SaaS
In the wild
Yes
MeetsMore confirms unauthorized logins and exploitation of its scheduling feature.

What happened

MeetsMore says an attacker used an accessed account to exploit its provider-availability feature on November 11–12. Up to 366,850 scheduling records may have leaked: addresses, phone numbers, member/request identifiers, internally registered meeting URLs and, for linked external calendars, event titles only. Names, emails, passwords and cards are excluded from this feature leak, not from every possible view through an accessed account.

The preceding 201 account intrusions could expose requesters’ registered names, emails and phone numbers, request history including addresses, and messages. Provider accounts could expose profiles, messages, schedules and associated customers’ names, addresses and requests. MeetsMore suspects credentials obtained elsewhere; it found no evidence of credentials leaking from its own systems. It confirmed neither profile changes, sent messages nor payment operations. No related misuse or secondary harm was confirmed as of disclosure. ProOne runs separately and is unaffected.

The vendor patched the server-side flaw; it published neither technical exploit details nor a customer-installable version. The record limit, login attempts and accessed accounts are different measures. Active exploitation and the disclosed data scope warrant the severity rating. This is separate from the KARTE breach; do not apply that notice’s no-reset guidance to accounts reset in this incident.

Crime-scene timeline

  1. Nov 11–12, 2026

    Account intrusions precede scheduling-data theft

    MeetsMore reports 812 login attempts, 201 accessed accounts and subsequent exploitation of the provider-availability feature using an accessed account.

  2. Nov 12, 2026

    MeetsMore blocks attackers, patches the flaw and resets affected accounts

    It invalidated affected passwords, signed those accounts out on every device and requested password resets. It also checked similar data-access functions.

  3. Nov 13, 2026

    Regulators and police notified

    MeetsMore reported to Japan's Personal Information Protection Commission and communications ministry and consulted police.

  4. Nov 16, 2026

    Public disclosure distinguishes account access from scheduling records

    Up to 366,850 potentially exposed records is not a confirmed unique-person count or a count of compromised accounts.

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.