Skip to content

Multiple Vulnerabilities in Pleasanter

Release date: November 17, 2026

Overview

The following four vulnerabilities have been found in Pleasanter.

  1. Information disclosure vulnerability involving API keys and other information in the API
  2. Path traversal vulnerability in the handling of attachments in the API
  3. Disclosure of non-public information in the Publishing Function
  4. Vulnerability that allows the values of columns whose reading is restricted by column access control to be viewed

All of these vulnerabilities are fixed in 1.5.10.0 (released November 17, 2026). For details of the countermeasures, see "Countermeasure".

Vulnerability 1: Information disclosure vulnerability involving API keys and other information in the API

Overview

A vulnerability has been found in the Pleasanter API that retrieves user information. It allows a general user to obtain the API keys and other information of other users (including administrators) in the same tenant.

Affected environments

1. Configurations that are not affected

If the API function is disabled, you are not affected by this vulnerability.

* The API function is disabled by either of the following settings.

  • "Enabled" in API.json is set to false (disabled for the entire system)
  • "Disable API" is checked in Tenant Management (disabled for each tenant)

For the settings, see the following manuals.

2. Affected versions

Versions 1.2.24.0 through 1.5.9.1 are affected. This applies to both Community Edition and Enterprise Edition.

Vulnerability description

In the API that retrieves user information, when a request was sent in a specific way, the values of columns that should not be returned to any user, including administrators (such as API keys and information related to two-factor authentication), were returned.
Any user who can log in to Pleasanter and use the API can exploit this. A third party who cannot log in cannot exploit it.

Threat posed by the vulnerability

By using an obtained API key, a malicious user can impersonate another user (including administrators) in the same tenant and run the API.
As a result, information registered in Pleasanter may be viewed, tampered with, or deleted with the permissions of the impersonated user.
Note that obtaining an API key, and viewing, tampering with, or deleting information by using the obtained API key, are recorded in the operation log (the user who ran the operation, and the date and time).

Vulnerability 2: Path traversal vulnerability in the handling of attachments in the API

Overview

A vulnerability has been found in the process that updates records through the Pleasanter API. It allows arbitrary files on the server to be obtained.

Affected environments

1. Affected versions

Version 1.5.9.1 and all earlier versions are affected. This applies to both Community Edition and Enterprise Edition.

Vulnerability description

When updating a record through the API, if crafted attachment information was specified, the location of the file was not properly checked, and arbitrary files on the server that Pleasanter can read could be obtained.
Any user who can update records in a site that has an attachment column and can use the API can exploit this. A third party who cannot log in cannot exploit it.

Threat posed by the vulnerability

A malicious user can obtain files on the server (such as configuration files that contain database connection information, and logs).
As a result, database connection information and other information may be disclosed.

Vulnerability 3: Disclosure of non-public information in the Publishing Function

Overview

A vulnerability has been found in sites published with the Publishing Function of Pleasanter. It allows a third party to obtain information that is not published.

Affected environments

1. Affected combinations

You are affected if both of the following apply.

  • A site is published with the Publishing Function
  • The published site has a link column (one that links to another site, or to users, groups, or departments)

If you do not use the Publishing Function, you are not affected by this vulnerability.

2. Affected versions

Version 1.5.9.1 and all earlier versions are affected. This applies to both Community Edition and Enterprise Edition.

Vulnerability description

In a published site, even if the site that a link column links to is not published, its records are displayed as options in the dropdown list.
When a request crafted into a form that normal operations do not send was sent to the process that retrieves these options, information beyond the options displayed in the published site was returned.
Anyone who can access the published site can exploit this, even a third party who is not logged in.

Threat posed by the vulnerability

A malicious third party can obtain information on linked records that are not displayed as options (the title and the columns merged into the title), as well as the names of users, groups, and departments registered in the same tenant.
As a result, information that is not published may be disclosed externally.

Vulnerability 4: Vulnerability that allows the values of columns whose reading is restricted by column access control to be viewed

Overview

A vulnerability has been found in which, for columns whose reading is restricted by column access control in Pleasanter, the restriction is not applied in some operations such as the API.

Affected environments

1. Affected settings

You are affected if a condition for reading is set in column access control.
This applies both when "Record users" (manager, owner, creator, updator) is specified on the "Others" tab and when users, groups, or departments are specified on the "General" tab.
The affected operations differ depending on how the condition is set. See "Workaround: Vulnerability 4" in "Countermeasure".

2. Affected versions

Version 1.5.9.1 and all earlier versions are affected. This applies to both Community Edition and Enterprise Edition.

Vulnerability description

When a condition for reading was set in column access control, the condition was not properly applied in the following operations, and the values of columns whose reading is restricted were returned even to users who do not meet the condition.

  • Retrieving records through the API
  • Exporting in JSON format (including site packages that contain data)
  • Retrieving through server scripts
  • The "Title and Body" column in the list
  • Custom design in the list
  • The content that appears in the index and results of cross search
  • The meta tags on the edit screen

Any user who can view the records of the target site can exploit this.

Threat posed by the vulnerability

A malicious user can view the values of columns (including the body) whose reading is restricted by column access control.
As a result, information whose viewing was restricted may be disclosed to users who do not meet the condition.

Countermeasure

1. For customers whose environment meets the conditions in "Affected environments"

Countermeasure: Version up

  • Please upgrade to 1.5.10.0 (released November 17, 2026) or later. It fixes all of the vulnerabilities above.
  • For the upgrade procedure, see the following manuals. Users with a contract for the Annual Support Service can consult us about upgrading through the dedicated web inquiry window.

Workaround: Vulnerability 1

  • You can avoid the impact of this vulnerability by customizing the column definitions so that columns such as the API key cannot be referenced. This does not affect normal use.
  • This workaround is effective in all environments that fall under "Affected environments" of Vulnerability 1.
  • Create Column.json in the App_Data/Parameters/CustomDefinitions folder, write the following content, and restart Pleasanter. If the folder does not exist, create it. If Column.json already exists, back up the file, and then add the following four items inside the { } of the existing JSON. If a definition with the same item name already exists, add the "ReadAccessControl" setting to that definition.

    {
        "Users_ApiKey": { "ReadAccessControl": "ManageService" },
        "Users_SecretKey": { "ReadAccessControl": "ManageService" },
        "Users_SecondaryAuthenticationCode": { "ReadAccessControl": "ManageService" },
        "Users_SecondaryAuthenticationCodeExpirationTime": { "ReadAccessControl": "ManageService" }
    }
    

Workaround: Vulnerability 4

For values whose reading you want to restrict by column access control, change the settings as appropriate so that they do not fall under the "Affected" combinations below.

Combination with a column whose reading is restricted When access control is set on the "Others" tab When access control is set on the "General" tab
Retrieving values through the API Affected Not affected
Setting "Export type" to "JSON" in "Export" of Manage Site (including exporting site packages that contain data) Affected Affected
Using the server script items.Get Affected Affected
Displaying the body (Body) on the edit screen (when you want to control the body) Affected Affected
Displaying title/body (TitleBody) in the list (when you want to control the body) Affected Affected
Using it in the custom design of the list Affected Not affected
Using cross search (when "Fulltext Types" in the advanced settings of the target column is other than "None") Affected Affected

If upgrading is difficult

  • If upgrading is difficult due to circumstances such as system operation, please contact us at the contact information below. We will ask about your environment and circumstances and advise you on how to respond.

2. For customers using the private cloud

  • We applied the fixed version on November 16, 2026. No action is required on your part.

3. For customers using Pleasanter.net

  • We applied the fixed version on November 9, 2026. No action is required on your part.

4. For customers using Shelter

  • We applied the fixed version on November 11, 2026. No action is required on your part.

Request after applying the countermeasure (Vulnerability 1)

Regardless of how you use Pleasanter, after the workaround is applied, after upgrading, or after we apply the fixed version, we recommend reissuing the API keys (and reconfiguring two-factor authentication as necessary) for all users who have issued an API key (including administrators).
Also apply the reissued API keys to the settings of the linked systems that use the API.
This is because, if API keys or other information were obtained before the countermeasure, the countermeasure alone cannot prevent impersonation using the obtained API keys.

Acknowledgments

Vulnerability 3 was reported by 碓氷 真之 of 株式会社IHI.
Vulnerability 4 was reported by 寺田 学, Representative Director of 株式会社CMSコミュニケーションズ.
We appreciate their cooperation.

Change log

2026.11.17 This vulnerability information has been made public.

Contact information

If you have any questions about this matter, please contact us via the form below.

Inquiry form: https://pleasanter.org/contact/