Security readout for executives and security teams
Plain-English summary
Glossword deployments running the affected standalone versions can let an administrator upload a file that the server later runs as PHP. Because exploitation requires administrator privileges, the main business risk is from compromised admin accounts, malicious insiders, or exposed admin panels. Successful exploitation can fully compromise the application server.
Executive priority
Prioritize legacy internet-facing Glossword systems immediately. The vulnerability is critical because admin-level access can become server code execution, and public exploit references exist. If no supported remediation path is available, isolation or migration should be treated as the practical business decision.
Technical view
The bundle describes CWE-434 in Glossword 1.8.8 through 1.8.12. The gw_admin.php administrative interface accepts uploads into gw_temp/a/ with insufficient file type and path validation, enabling uploaded PHP execution and remote code execution when deployed standalone.
Likely exposure
Exposure is most likely in legacy Glossword standalone installations with reachable gw_admin.php and valid administrator accounts. The structured affected data only explicitly lists version 1.8.8, while the description names 1.8.8 through 1.8.12, so version scoping should be verified locally.
Exploitation context
The source bundle cites public exploit references, including Exploit-DB and Metasploit module URLs. It does not mark the CVE as KEV, and no provided source establishes active exploitation in the wild. Treat public exploit availability as a serious risk multiplier, especially for internet-reachable admin panels.
Researcher notes
Evidence is strong for the vulnerability class and attack path, but remediation details are incomplete in the provided bundle. Avoid overstating active exploitation: KEV is false here. Pay close attention to the discrepancy between the narrative version range and the structured affected record.
Mitigation direction
- Identify and remove unsupported or unused Glossword standalone deployments.
- Check vendor or project guidance before assuming a fixed version exists.
- Restrict gw_admin.php access to trusted networks and administrators only.
- Harden authentication for administrator accounts and review account ownership.
- Prevent PHP execution from upload and temporary directories where feasible.
- Inspect gw_temp/a/ and adjacent upload paths for unexpected executable files.
Validation and detection
- Inventory Glossword instances and confirm exact deployed versions.
- Verify whether gw_admin.php is reachable from untrusted networks.
- Review administrator accounts for stale, shared, or suspicious access.
- Inspect gw_temp/a/ for unexpected PHP or executable content.
- Review web and application logs for unusual administrative upload activity.
- Confirm upload directories cannot execute server-side scripts.
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.
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 lookupExecution 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 lookupFile 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 lookupCVE-2013-10067 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
- Critical
- CVSS
- 9.4 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
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 vector scores
1 official scoreWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Source materials
- CVE List V5 sourceCVE List V5
- https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/multi/http/glossword_upload_exec.rbCVE reference · exploit
- https://www.exploit-db.com/exploits/24456CVE reference · exploit
- https://www.exploit-db.com/exploits/24548CVE reference · exploit
- https://github.com/glosswordteam/GlosswordCVE reference · product
- https://sourceforge.net/projects/glossword/CVE reference · product
- https://www.vulncheck.com/advisories/glossword-arbitrary-file-upload-rceCVE reference · third-party-advisory
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.
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.