PHP Vulnerability Responses by Company

RAKUS

Japan-based services
Aliases / services
株式会社ラクス / RAKUS / 楽楽精算 / 楽楽明細 / 楽楽販売 / 楽楽勤怠 / 楽楽自動応対 / 楽楽メールマーケティング / Chat Dealer / クルメル / ラクテル
Official website
https://www.rakus.co.jp/

Each response applies only to its stated service scope. “Not listed” does not mean unpatched or unaffected.

Response status by service

Rakuraku Seisan

Response status
No response required
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

Business cloud services including the Rakuraku series.

The 22 October official table lists Rakuraku Seisan as requiring no response and operating normally.

Scope: This product only. The notice does not disclose the technical reason.

What users should do

Use normally.

Official service URL

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlService and operation documentation
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

楽楽明細

Response status
No response required
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The 22 October official table lists 楽楽明細 as requiring no response and operating normally.

Scope: 楽楽明細 only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlService and operation documentation
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

楽楽請求

Response status
No response required
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The 22 October official table lists 楽楽請求 as requiring no response and operating normally.

Scope: 楽楽請求 only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlService and operation documentation
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

楽楽電子保存

Response status
No response required
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The 22 October official table lists 楽楽電子保存 as requiring no response and operating normally.

Scope: 楽楽電子保存 only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlService and operation documentation
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

楽楽債権管理

Response status
No response required
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The 22 October official table lists 楽楽債権管理 as requiring no response and operating normally.

Scope: 楽楽債権管理 only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlService and operation documentation
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

楽楽人事労務

Response status
No response required
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The 22 October official table lists 楽楽人事労務 as requiring no response and operating normally.

Scope: 楽楽人事労務 only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlService and operation documentation
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

楽楽従業員ポータル

Response status
No response required
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The 22 October official table lists 楽楽従業員ポータル as requiring no response and operating normally.

Scope: 楽楽従業員ポータル only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlService and operation documentation
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

楽楽販売

Response status
Response completed; restored
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The provider announced 楽楽販売 restored on 22 October after preventive maintenance and safety checks.

Scope: 楽楽販売 only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlResponse evidence
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

楽楽勤怠

Response status
Response completed; restored
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The provider announced 楽楽勤怠 restored on 22 October after preventive maintenance and safety checks.

Scope: 楽楽勤怠 only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlResponse evidence
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

楽楽自動応対

Response status
Response completed; restored
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The provider announced 楽楽自動応対 restored on 22 October after preventive maintenance and safety checks.

Scope: 楽楽自動応対 only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlResponse evidence
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

楽楽メールマーケティング

Response status
Response completed; restored
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The provider announced 楽楽メールマーケティング restored on 22 October after preventive maintenance and safety checks.

Scope: 楽楽メールマーケティング only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlResponse evidence
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

ChatDealer

Response status
Response completed; restored
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The provider announced ChatDealer restored on 22 October after preventive maintenance and safety checks.

Scope: ChatDealer only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlResponse evidence
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

クルメル

Response status
Response completed; restored
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The provider announced クルメル restored on 22 October after preventive maintenance and safety checks.

Scope: クルメル only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlResponse evidence
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation

楽テル

Response status
Response completed; restored
Response information checked
2026-10-28

Current re-audit: Official response verified · Research date: 2026-10-28

The provider announced 楽テル restored on 22 October after preventive maintenance and safety checks.

Scope: 楽テル only. Technical details/PHP version are undisclosed; the separate subsidiary's blastmail incident is excluded.

What users should do

Normal use is available.

Source URLs

  1. PHP response for RAKUS cloud serviceshttps://www.rakus.co.jp/news/2026/1022-2.htmlResponse evidence
  2. https://www.rakus.co.jp/news/2026/1022-1.htmlhttps://www.rakus.co.jp/news/2026/1022-1.htmlResponse evidence
  3. https://www.rakus.co.jp/news/https://www.rakus.co.jp/news/Service and operation documentation
  4. https://www.rakus.co.jp/company/history/https://www.rakus.co.jp/company/history/Service and operation documentation
Related official sources
  1. PHP response for RAKUS cloud servicesOfficial notice
  2. Company and operator informationOfficial information directory

Comments