The Webinfos WordPress plugin through 1.2 does not validate the type or name of uploaded files, nor restrict the upload action with any authentication, capability, or nonce check, allowing unauthenticated attackers to upload arbitrary files (including PHP) to a web-accessible directory, leading to remote code execution on servers that execute PHP from the uploads path.
Security readout for executives and security teams
Plain-English summary
A reported flaw in the Webinfos WordPress plugin through version 1.2 lets unauthenticated internet users upload arbitrary files. If the server executes PHP in the upload directory, an attacker could take control of the website, alter data, steal information, or disrupt service.
Executive priority
Treat as an immediate remediation priority for internet-facing sites. Unauthenticated remote code execution can enable complete website and server compromise. Isolate affected systems and begin incident review if suspicious uploads or requests are found.
Technical view
The upload handler reportedly lacks file type and filename validation, authentication, capability checks, and nonce verification. This is CWE-434 with CVSS 3.1 score 9.8. Arbitrary PHP upload can become remote code execution when the destination is web-accessible and configured to execute PHP.
Likely exposure
Internet-accessible WordPress sites running Webinfos through 1.2 are potentially exposed. Code execution depends on whether uploaded PHP files are web-accessible and executable. The bundle’s affected-product metadata is incomplete and conflicts with the description, so inventory confirmation is essential.
Exploitation context
The source bundle marks the WPScan reference as exploit-related, but provides no evidence of exploitation in the wild. The CVE is not listed as KEV in the supplied data. Treat it as readily exploitable based on network access, low complexity, and no required authentication or user interaction.
Researcher notes
The supplied description says versions through 1.2 are affected, while structured affected data lists only version 0 with unknown default status. No patched version or vendor mitigation is provided. Confirm product identity, installed version, upload path behavior, and server-side PHP execution before closing exposure.
Mitigation direction
Identify and prioritize every WordPress site running Webinfos through version 1.2.
Disable or remove the plugin until vendor guidance confirms a safe release.
Prevent PHP execution in web-accessible upload directories where operationally feasible.
Restrict unnecessary public access to the affected upload endpoint.
Check vendor and WPScan guidance for verified remediation or updated versions.
Validation and detection
Confirm installed Webinfos versions across production, staging, and legacy WordPress sites.
Verify whether the upload destination is publicly reachable and executes PHP files.
Review web logs for suspicious unauthenticated requests to the plugin’s upload functionality.
Inspect upload directories for unexpected PHP files or recently created executable content.
After remediation, confirm the vulnerable upload action is unavailable to unauthenticated users.
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.
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.
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.
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
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical 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.
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.