LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47890: pyLoad 0.5.0 is vulnerable to Unrestricted File Upload.

pyLoad 0.5.0 is vulnerable to Unrestricted File Upload.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-47890 describes an unrestricted file upload issue in pyLoad 0.5.0. A low-privileged authenticated user could potentially upload files in a way that affects confidentiality, integrity, and availability. The supplied sources rate it high severity, but do not prove active exploitation or name a specific fixed release.

Executive priority

Treat as high priority where pyLoad is deployed, especially if reachable by users outside trusted administration groups. No active exploitation is proven in the supplied sources, but the potential business impact is high and version exposure should be confirmed quickly.

Technical view

The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, indicating network exploitation by an authenticated attacker without user interaction. The source bundle labels the weakness as CWE-22 and describes unrestricted file upload in pyLoad 0.5.0. Product/version metadata is incomplete beyond that description.

Likely exposure

Likely exposure is pyLoad 0.5.0 instances reachable over a network where attackers can obtain or use valid credentials. The bundle’s formal affected-product fields are incomplete, so teams should verify installed pyLoad versions against the CVE record and GitHub advisory.

Exploitation context

The source bundle does not cite CISA KEV listing or any public evidence of active exploitation. Risk remains material because the CVSS vector indicates low complexity, network reachability, and high confidentiality, integrity, and availability impact after authentication.

Researcher notes

The bundle is sparse: it names pyLoad 0.5.0 and an unrestricted file upload issue, but the affected-product fields are n/a and no fix is included. The record was updated on 2026-07-09, so researchers should verify whether the GitHub advisory now provides additional version or remediation detail.

Mitigation direction

  • Check the pyLoad GitHub advisory for vendor-confirmed upgrade or remediation guidance.
  • Identify and prioritize any pyLoad 0.5.0 deployments.
  • Restrict network access to pyLoad administrative or upload interfaces.
  • Review accounts and remove unnecessary low-privileged access.
  • Monitor pyLoad logs for unexpected uploads or file path activity.

Validation and detection

  • Inventory systems for pyLoad and record exact installed versions.
  • Confirm whether any pyLoad service is internet-facing or broadly reachable internally.
  • Review the GitHub advisory and CVE record for affected-version clarification.
  • Check authentication logs for suspicious low-privileged account activity.
  • Inspect upload directories for unexpected files or path anomalies.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-47890 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-47890Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.