Skip to content
TrustList
Security advisories

Pleasanter 1.5.10.0 fixes API flaw that leaks administrator keys

Editorial

By TrustList Editorial

Three of the four flaws need a logged-in account; the fourth lets anyone who can reach a published site read record titles and user names from unpublished ones.

About Pleasanter 1.5.10.0 fixes API flaw that leaks administrator keys

Pleasanter 1.5.10.0 fixes API flaw that leaks administrator keys

17 November 2026: Implem has released Pleasanter 1.5.10.0 to fix four vulnerabilities in its low-code business application platform, the most serious of which, CVE-2026-125276 (CVSS 4.0 score 7.1), lets a logged-in user obtain other users' credentials, including administrators' API keys, through a crafted API request. The advisory, published by Japan's JVN, does not report exploitation.

Not yet independently verified. Scores, affected versions and the fix are from the JVN advisory published by JPCERT/CC and IPA. We did not read Implem's own Japanese advisory, so the workaround it offers is not described here, and neither source reports exploitation. We will update this when it can be confirmed, and remove this note.

Four CVEs and the versions they reach

The advisory lists each flaw with its CVSS 4.0 and 3.0 base scores:

CVE Flaw CVSS 4.0 CVSS 3.0 Affected
CVE-2026-125276 Sensitive information sent in API responses 7.1 6.5 1.2.24.0 to 1.5.9.1
CVE-2026-117634 Incorrect authorisation in the Publishing feature 6.9 5.3 1.5.9.1 and earlier
CVE-2026-121811 Path traversal in the API 5.3 4.3 1.5.9.1 and earlier
CVE-2026-125411 Incorrect authorisation in item access control 5.3 4.3 1.5.9.1 and earlier

All four are fixed in 1.5.10.0.

The API is on by default

Two of the flaws sit in the API. With CVE-2026-125276 an authenticated attacker can collect other accounts' credentials and then, in JVN's words, perform arbitrary operations "with the privileges associated with the obtained credentials". With CVE-2026-121811 an authenticated attacker can fetch an arbitrary file from the server. JVN notes that the API is enabled by default and that installations with it disabled are not affected by either flaw.

That makes any account a route to administrator rights on an unpatched server, so a site where many staff or outside partners have logins is more exposed than one with a handful of users. After updating, administrators should reissue API keys, because a key copied before the fix keeps working.

Published sites leak names from private ones

CVE-2026-117634 is the only flaw that needs no login. Where a site is published with the Publishing feature and contains link items, meaning items linked to other sites, users, groups or organisations, an outsider can obtain the titles of records on unpublished sites and the names of users, groups and organisations in the same tenant.

CVE-2026-125411 affects configurations that restrict reading of particular items through column access control: a user who can view the records can read the restricted values anyway. Teams that rely on that setting to hide salary, pricing or personal fields should treat those values as visible to every record viewer until the update is applied.

If the update has to wait

JVN says the developer recommends a workaround where the update cannot be applied and directs users to Implem for the details. Disabling the API, where nothing depends on it, removes the two API flaws by JVN's own description.

The flaws were reported by Masayuki Usui of IHI Corporation and Manabu Terada of CMS Communications and coordinated by IPA and JPCERT/CC. Implem is listed in our catalogue at Implem, and the low code development platform software category lists 13 products.

Related on TrustList:

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in