LiveActive security incident?Get immediate response
CVE Record

CVE-2012-10019: Front-end Editor < 2.3 - Arbitrary File Upload

The Front End Editor plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation via the upload.php file in versions before 2.3. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected sites server which may make remote code execution possible.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This affects the WordPress Front-end Editor plugin before version 2.3. A missing upload file-type check could let an unauthenticated internet user place arbitrary files on the server, which may lead to full site compromise. The bundle does not show confirmed active exploitation.

Executive priority

Prioritize remediation for internet-facing WordPress sites using this plugin. The issue can be exploited without credentials and may enable remote code execution, making it urgent where the vulnerable component is present.

Technical view

The vulnerability is CWE-434 in Front-end Editor upload.php. The CVSS 3.1 score is 9.8 because exploitation is network-accessible, low complexity, unauthenticated, and requires no user interaction. Impact is high for confidentiality, integrity, and availability if arbitrary uploads become executable server-side content.

Likely exposure

Exposure is limited to WordPress sites running the Front-end Editor plugin before 2.3 with the vulnerable upload handler reachable. Sites without this plugin, or on non-vulnerable versions, are not indicated as affected by the bundle.

Exploitation context

Public advisories and a Packet Storm reference exist, so technical details have been publicly known. The source bundle marks KEV as false and provides no cited evidence of current active exploitation. The risk remains high because unauthenticated upload flaws are commonly severe.

Researcher notes

The provided affected metadata is sparse, but the title and description identify Front-end Editor before 2.3. Do not infer broader WordPress impact. Validate presence, version, reachability of upload.php, and any evidence of unexpected uploaded files.

Mitigation direction

  • Upgrade Front-end Editor to version 2.3 or later where available.
  • Disable or remove the plugin if it is not required.
  • Check vendor or WordPress plugin guidance for current support status.
  • Audit the server for unexpected files in plugin-accessible upload locations.
  • Treat suspicious uploaded executable content as potential compromise.

Validation and detection

  • Inventory WordPress sites for the Front-end Editor plugin.
  • Confirm installed plugin versions are not earlier than 2.3.
  • Review web server logs for unexpected access to upload.php.
  • Inspect plugin upload locations for unfamiliar executable files.
  • Verify remediation by confirming the plugin is updated, disabled, or removed.
Prepared
Confidence
high
Sources
7

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-2012-10019 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
6Source 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-2012-10019Attack 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
scribuFront-end Editor0unaffected
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.