Pleasanter
CVE-2025-58070
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessUpload crafted attachment with script payload
-
DeliveryPayload stored in Pleasanter record
-
ExploitVictim opens attachment Preview
-
ExecutionScript executes in victim's browser session
-
ImpactSession/data compromised in victim context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an attacker to store a malicious script via an uploaded file that is rendered through Pleasanter's Preview for Attachments feature, and a logged-in victim must then actively open that preview (UI:A) for the script to fire. Limiting factors: the payload only executes in the browser of an authenticated user who interacts with the preview (no server-side impact), and placing the attachment generally requires upload access to a Pleasanter record/site - in typical deployments that means an authenticated account, which narrows the realistic attacker set despite the vendor's PR:N rating. |
| Impact | This is a medium-severity stored XSS (CWE-79) with modest real-world risk signals that largely agree. The vendor-supplied CVSS 4.0 vector (base score 5.1) shows network attack vector, low complexity, no attack requirements, no privileges (PR:N) and required active user interaction (UI:A), with no impact to the vulnerable system itself (VC:N/VI:N/VA:N) but low subsequent-system confidentiality and integrity impact (SC:L/SI:L) - consistent with script execution in a victim's authenticated browser session rather than server compromise. EPSS is low (0.20%, 9th percentile), there is no CISA KEV listing and no public exploit identified at time of analysis, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The signals are consistent: a stored XSS requiring a victim to preview a malicious attachment, bounded impact, low probability - this is a routine patch-in-normal-cycle issue, not an emergency. One caveat to verify: the vendor rates privileges as PR:N, but storing a malicious attachment in Pleasanter typically presupposes the ability to upload a file, which in most deployments requires an authenticated/authorized account - the PR:N rating may assume a configuration allowing anonymous or low-trust uploads, so operators should confirm their upload exposure. |
| Exploit ScenarioDerived | An attacker uploads a file crafted with a malicious script payload as an attachment within Pleasanter; when a logged-in user opens the attachment's Preview feature, the stored script executes in that user's browser session, enabling session/data theft or actions in the victim's context. Exploitation requires the victim to actively view the preview (UI:A). No public proof-of-concept exploit was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Stored cross-site scripting in Pleasanter's Preview for Attachments lets an attacker embed a script in an uploaded file that executes in the browser of a logged-in user who opens that preview. Victims are Pleasanter deployments that render attachment previews; exploitation requires the attacker to place a crafted file (in typical deployments an account with upload rights on a record or site, i.e., an authenticated user) plus a victim who actively opens the preview. No public exploit code has been identified and there is no confirmed active exploitation; the vendor's CVSS 4.0 base score is 5.1 and EPSS is low at 0.20% (9th percentile), consistent with the medium-severity independent assessment.
RemediationAI
Patch available per vendor advisory: Pleasanter published a vulnerability update on 24 October 2025 (https://pleasanter.org/archives/vulnerability-update-20251024), mirrored by JVN advisory JVN20611740 (https://jvn.jp/en/jp/JVN20611740/) - apply the fixed build specified there, since no exact version identifier or upstream commit was provided in the input. Until the upgrade is deployed, reduce exposure by restricting who can upload attachments to records and sites to trusted, vetted roles, which collapses the realistic attacker set given that placement of the malicious file generally requires an authenticated account; note this does not eliminate risk if untrusted staff legitimately require upload rights. If inline attachment previews are not operationally essential, disable the Preview for Attachments feature (or the file-preview path) - the trade-off is loss of convenience and potential workflow disruption for users who rely on in-page previews. Deploy a strict Content-Security-Policy that disallows inline and third-party script execution on Pleasanter pages, understanding that this requires testing because it can break legitimate UI scripting, and ensure session cookies are marked HttpOnly and SameSite so that any successful script execution cannot trivially exfiltrate session tokens - HttpOnly limits token theft but does not stop script execution or same-origin requests, so it is a containment measure only. Because this is a stored XSS, also consider server-side validation or sanitization of uploaded file contents/types as a compensating control, and monitor for anomalous upload activity.
Affected ProductsAI
Pleasanter, the web-based low-code application/database platform distributed by Pleasanter (Implem), in the versions identified in the vendor's vulnerability update published 24 October 2025 (https://pleasanter.org/archives/vulnerability-update-20251024) and mirrored in the JVN advisory JVN20611740 (https://jvn.jp/en/jp/JVN20611740/). No CPE data or explicit version range was included in the supplied intelligence, so deployments should map their installed Pleasanter build against the vendor advisory to determine exposure; the flaw specifically concerns instances where the Preview for Attachments capability is enabled and users can open attachment previews in the browser.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is a classic stored/persistent cross-site scripting flaw (CWE-79, improper neutralization of input during web page generation) in Pleasanter, a low-code web application and database platform. The Preview for Attachments feature renders uploaded file content back into a browser context without sufficient output encoding or sanitization, so script-bearing content persists server-side and fires whenever a user views the preview. The vendor's CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:A, with S:C and SC:L/SI:L) frames this as network-reachable with victim interaction and low subsequent-system confidentiality/integrity impact; the independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, treating the upload/placement step as typically requiring an authenticated account and treating scope as changed because the script executes in the victim's browser session rather than the server's origin. No CPE strings were supplied, so the exact affected product identifiers must be confirmed from the vendor advisory and the JVN entry (JVN20611740).
Know when Pleasanter gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Storing the attachment realistically needs upload privileges (PR:L); victim must open the preview (UI:R); script runs in the browser crossing a trust boundary (S:C) with limited C/I impact and no availability loss.
Primary rating from Vendor (jpcert).
CVSS VectorVendor: jpcert
DescriptionCVE.org
Pleasanter contains a stored cross-site scripting vulnerability in Preview for Attachments, which allows an attacker to execute an arbitrary script in a logged-in user's web browser.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Pleasanter
View allCross-site scripting vulnerability in Pleasanter 1.3.38.1 and earlier allows a remote authenticated attacker to inject a
Pleasanter's LDAP authentication path can grant access when a request supplies a valid Login ID but no password, letting
Directory traversal vulnerability in Pleasanter (Community Edition and Enterprise Edition) 1.3.39.2 and earlier versions
Pleasanter 1.3.49.0 and earlier contains a cross-site scripting vulnerability. Rated medium severity (CVSS 6.1), this vu
Open redirect vulnerability in Pleasanter 1.3.47.0 and earlier allows a remote unauthenticated attacker to redirect user
Pleasanter 1.3.47.0 and earlier contains a stored cross-site scripting vulnerability. Rated medium severity (CVSS 5.4),
Stored cross-site scripting vulnerability in Pleasanter (Community Edition and Enterprise Edition) 1.3.39.2 and earlier
Stored cross-site scripting in the Pleasanter no-code business application platform lets an authenticated low-privilege
Pleasanter 1.3.47.0 and earlier contains an improper access control vulnerability, which may allow a remote authenticate
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB