LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36424: An issue discovered in phpwcms 1.9.25 allows remote attackers to run arbitrary code via DB user field durin...

An issue discovered in phpwcms 1.9.25 allows remote attackers to run arbitrary code via DB user field during installation.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-36424 is a critical phpwcms issue reported for version 1.9.25. During installation, a remote unauthenticated attacker could run arbitrary code through the database user field. The main business risk is full compromise of a site if an affected installer is reachable.

Executive priority

Prioritize same-day assessment for any internet-facing phpwcms estate. If phpwcms 1.9.25 or an exposed installer is found, reduce exposure immediately and follow vendor guidance before relying on normal monitoring.

Technical view

The CVE describes CWE-94 code injection in phpwcms 1.9.25. The vulnerable condition is tied to installer handling of the DB user field. CVSS 3.1 is 9.8, network reachable, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on phpwcms 1.9.25 deployments where the installation workflow remains accessible. The structured affected-product data is incomplete and lists n/a, so teams should confirm phpwcms usage and version directly.

Exploitation context

The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The issue is still urgent because the CVSS vector indicates unauthenticated remote code execution when the vulnerable installer path is reachable.

Researcher notes

Evidence is narrow: CVE data and a referenced GitHub issue identify installer DB user field code execution, but the bundle does not provide fixed versions, exploit maturity, or complete CPE coverage. Validate behavior in a controlled environment without publishing weaponized details.

Mitigation direction

  • Check phpwcms vendor guidance for a fixed version or official mitigation.
  • Remove or disable installation components after setup is complete.
  • Block public access to any remaining installation workflow.
  • Upgrade affected phpwcms 1.9.25 deployments when a vendor-supported fix is identified.
  • Treat any exposed affected installer as potentially compromised until reviewed.

Validation and detection

  • Inventory sites for phpwcms and confirm exact installed version.
  • Verify whether installation functionality is reachable from untrusted networks.
  • Review access logs for unexpected installation workflow requests.
  • Confirm installer files or routes are removed or access-controlled after setup.
  • Check integrity of phpwcms files and configuration on exposed systems.
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-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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
cve · low confidence lookup

CVE-2021-36424 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2021-36424Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.