Security readout for executives and security teams
Plain-English summary
PartKeepr 1.4.0 has a stored cross-site scripting issue involving the name parameter in edit-related API endpoints. A malicious stored value could execute in another user's browser when viewed. The public sources do not provide CVSS, a confirmed patch, or evidence of active exploitation.
Executive priority
Treat this as a targeted application risk requiring inventory and containment, not an emergency exploitation event based on current evidence.
Technical view
CVE-2021-39390 describes stored XSS in PartKeepr 1.4.0, affecting the Edit section across multiple API endpoints through the name parameter. The CVE record lists limited affected-product metadata and no CWE or CVSS details. KEV status is false in the provided bundle.
Likely exposure
Exposure is most likely limited to organizations running PartKeepr 1.4.0. The sources do not define authentication requirements, internet exposure, affected endpoint names, or whether later versions are fixed.
Exploitation context
No provided source reports active exploitation, and the CVE is not marked KEV. Public disclosure exists through the CVE records and the PartKeepr GitHub issue, but exploit maturity is not established.
Researcher notes
The record is sparse: no CVSS, CWE, endpoint list, authentication context, or patch statement is included. Analysis should stay tied to PartKeepr 1.4.0 and the name parameter until stronger vendor or maintainer evidence is available.
Mitigation direction
- Identify any deployed PartKeepr 1.4.0 instances.
- Review the PartKeepr issue and vendor/project guidance for fixes.
- Restrict access to PartKeepr administration and edit workflows.
- Remove suspicious stored values from name fields.
- Monitor logs for unusual edit activity.
- Consider migration if maintained fixes are unavailable.
Validation and detection
- Confirm the deployed PartKeepr version.
- Review whether edit API workflows are reachable by untrusted users.
- Inspect stored name values for suspicious markup or script content.
- Check application logs for recent unusual edits.
- Track the GitHub issue for project-level remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-39390 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://demo.partkeepr.org/CVE reference · x_refsource_MISC
- https://partkeepr.org/CVE reference · x_refsource_MISC
- https://github.com/partkeepr/PartKeepr/issues/1237CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.