Download Latest Version OpenEstate v0.9.1 -- Cheque Queue Validation Fix source code.zip (2.5 MB)
Home / v0.8.5
Name Modified Size InfoDownloads / Week
Parent folder
OpenEstate v0.8.5 -- Security Update source code.tar.gz 2026-11-03 1.9 MB
OpenEstate v0.8.5 -- Security Update source code.zip 2026-11-03 2.5 MB
README.md 2026-11-03 5.0 kB
Totals: 3 Items   4.4 MB 0

Security advisory: GHSA-vfmf-36cm-8fg7

A security release. Every install should upgrade. It needs a newer browser: read "Browser support" first. Advisory: GHSA-vfmf-36cm-8fg7.

What was wrong

Both problems need two people using the same browser profile, for example a shared office computer or a customer kiosk. Neither lets anyone reach another browser or device. Affected: all versions up to 0.8.4.

Data from the previous sign-in could show up in the same tab

The staff app and the customer/broker portal kept the data they had loaded (profiles, bookings, payments, form drafts) in one store in the page's memory for as long as the page stayed open. When one person signed out and another signed in without reloading the page, the second person could briefly see the first person's data. A slow reply meant for the first person could also appear on the second person's screen.

A tab could switch to another account and repeat a request as that account

Each app keeps one sign-in cookie per browser, shared by all its tabs. Suppose tab A is signed in as one account and someone signs in as a different account in tab B. When tab A's short-lived access expired, it renewed its sign-in with the shared cookie, received tab B's account, and sent its waiting request again as that account, saves included, while still showing tab A's screens.

What changed

  • Every sign-in gets its own empty store. Signing in, signing out, or a session being ended starts a new one. The previous store is thrown away, its requests are cancelled, and a reply that still arrives late is discarded. An ordinary renewal of the same sign-in keeps the store, so forms and loaded pages survive it.
  • A tab accepts renewed access only for the same account. The user, company and app must match, and on the portal the same customer or broker. If they don't, the tab:
  • signs itself out and shows "Your session has changed. Please sign in again.", without naming either account;
  • never sends the waiting request again, for reads and saves alike;
  • leaves the other account signed in and its cookie in place, so the other tab keeps working.

Browser support

The fix uses a browser feature (AbortSignal.any) that older browsers lack. Signed-in pages need one of these, or newer:

  • Chrome or Edge 116
  • Firefox 124
  • Safari 17.4

On older browsers they fail to load data. Only Chromium was tested; Firefox and Safari were not.

Upgrading

:::bash
cd /opt/openestate-src/deploy/native
sudo ./upgrade-native.sh --ref v0.8.5

Always give the release tag, never a branch name such as master.

  • Upgrading from v0.8.4 is supported.
  • No migrations, no new environment variable and no permission changes.
  • Install, backup, restore and uninstall are unchanged.
  • People who are signed in stay signed in. Open pages keep running the old code until they are reloaded.

Known limitations

  • A tab notices another tab's account change only when it renews its access: on its first request after its access expires (15 minutes by default), or on a reload. Until then it keeps working as its own account, because its access really is that account's.
  • Signing out in one tab still ends the shared sign-in for the other tabs of the same app in that browser, as before.
  • A wrong 2FA code entered while another account is signed in in the same browser shows "Your session has changed" instead of "Invalid TOTP code".
  • A "This operation was aborted" message can appear on a few staff screens after a sign-out interrupts one of their requests. No data is affected.

How it was checked

  • Browser tests in Chromium cover both problems and pass with the fix:
  • two tabs sharing one cookie, for reads and saves, on staff and portal;
  • switching between customers and brokers;
  • switching within one company and across companies;
  • late replies;
  • sign-out, 2FA, and sessions ended by an administrator.
  • The full suite was run on the fix from a clean clone, against a test database of its own: 1,191 unit and integration tests, 84 browser tests, and the 30 sign-in and security browser tests again with React's development checks on. None failed or was skipped.
  • An independent review of the change found no security defect.

CI note

On the release commit, 6 of the 8 CI jobs passed, including the clean upgrade from v0.8.4. Two upgrade variants failed because they test something this release does not contain: the lock-timeout variant expects a migration to wait on a locked table, and the orphan variant plants a row that v0.8.4 already refuses. v0.8.5 has no migrations. Both variants will be made version-aware in a later change. The upgrade was also rehearsed on a test server restored from v0.8.4.

Source: README.md, updated 2026-11-03