LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36426: File Upload vulnerability in phpwcms 1.9.25 allows remote attackers to run arbitrary code via crafted file...

File Upload vulnerability in phpwcms 1.9.25 allows remote attackers to run arbitrary code via crafted file upload to include/inc_lib/general.inc.php.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

phpwcms 1.9.25 is reported to allow a logged-in remote attacker to upload a crafted file that can lead to arbitrary code execution. If exploited, this could let an attacker take control of the affected website and its hosted data.

Executive priority

Treat this as a high-priority website platform risk where phpwcms 1.9.25 is present. It is not KEV-listed in the provided data, but the potential impact is full site compromise.

Technical view

The CVE describes a CWE-434 file upload flaw in phpwcms 1.9.25 affecting include/inc_lib/general.inc.php. CVSS 3.1 is 8.8, network-reachable, low complexity, low privileges required, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where phpwcms 1.9.25 is deployed and reachable by users who can authenticate and access file upload functionality. The structured affected-product metadata is incomplete, so asset validation is important.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates exploitation requires low privileges, but no user interaction, making compromised or low-trust accounts a meaningful concern.

Researcher notes

Evidence is limited to the CVE description, CVSS data, CWE-434 classification, and a GitHub issue reference. The affected-product fields are marked n/a despite the description naming phpwcms 1.9.25, so confirm scope directly in assets and vendor materials.

Mitigation direction

  • Identify any phpwcms 1.9.25 deployments and prioritize them for review.
  • Check phpwcms project guidance and upgrade if an official fixed release is identified.
  • Restrict upload-capable accounts to trusted users until remediation is confirmed.
  • Disable or tightly limit file upload functionality if business operations allow.
  • Review server controls that prevent execution of uploaded content where applicable.

Validation and detection

  • Confirm deployed phpwcms versions, especially internet-facing instances.
  • Review who can authenticate and upload files in phpwcms.
  • Check application and web logs for suspicious upload activity.
  • Look for unexpected changes near include/inc_lib/general.inc.php.
  • Track the referenced GitHub issue for project-specific remediation details.
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-434: 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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-2021-36426 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
0Timeline events
0ADP providers
2Source links

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.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2021-36426Attack 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
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.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.