Skip to content
Fencer Intel
high 7.4

CVE-2026-107644 json

Bizuno Accounting <= 7.4.5 - Unauthenticated Authentication Bypass via Password Reset Token Disclosure via 'bizUser' Parameter on portal/api/lostPW

published 13h ago modified 11h ago also EUVD-2026-128847

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

The Bizuno Accounting – ERP/Accounting/CRM (for WordPress) plugin for WordPress is vulnerable to Authentication Bypass via Password Reset Token Disclosure in all versions up to, and including, 7.4.5 via the `bizUser` parameter of the `validateReset()` function on the `portal/api/lostPW` endpoint. This is due to `portalCtl::goAPI()` failing to call `loadBusinessCache()` before invoking the handler, which causes `isMailConfigured()` to read an empty business cache and return false regardless of the site's actual mail configuration, causing the fully-qualified reset URL — containing the victim's live reset UUID and numeric user ID — to be embedded directly in the HTML response rather than delivered by email. This makes it possible for unauthenticated attackers to obtain a valid password-reset token for any Bizuno account, including administrators, directly from the HTTP response and submit it to the `portal/api/lostVal` endpoint to rewrite the victim's password and achieve full account takeover. The administrator email address required to initiate the reset is frequently exposed by the plugin's own login error messages and the public `/bizuno/` portal page, making exploitation trivial against most installations.

Is CVE-2026-107644 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
12h ago

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

  • phreesoft Bizuno Accounting – ERP/Accounting/CRM (for WordPress)

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.