The FacturaONE para WooCommerce con VeriFactu WordPress plugin before 5.37 does not authenticate one of its request handlers, whose only protection is derived from a cryptographic key that is empty in the default, unconfigured state, allowing unauthenticated attackers to write an arbitrary file into a web-accessible directory and achieve remote code execution.
Security readout for executives and security teams
Plain-English summary
A flaw in FacturaONE para WooCommerce con VeriFactu before version 5.37 may let an internet attacker take control of a WordPress server without logging in. Risk is greatest when the plugin remains unconfigured because its protective cryptographic key is empty by default.
Executive priority
Treat this as an immediate remediation priority for exposed WordPress sites. Rapidly identify affected installations, update or disable the plugin, and investigate potentially exposed servers. The possible outcome is full server compromise, although active exploitation is not confirmed by the supplied evidence.
Technical view
An unauthenticated request handler relies on a cryptographic-key-derived control. In the default unconfigured state, that key is empty, allowing arbitrary file creation in a web-accessible directory and potential remote code execution. CVE-2026-14289 is rated CVSS 9.0, with high confidentiality, integrity, and availability impact.
Likely exposure
Potentially exposed systems are WordPress sites running plugin versions earlier than 5.37, particularly internet-facing installations left in the default unconfigured state. The supplied structured affected-version metadata is inconsistent with the narrative, so asset owners should verify installed versions directly.
Exploitation context
The supplied WPScan reference is tagged for exploit information, but the bundle does not establish active exploitation. The CVE is not listed as KEV in the provided data. Attack complexity is rated high, but successful exploitation could provide remote code execution without credentials or user interaction.
Researcher notes
The narrative identifies versions before 5.37, while the structured affected entry lists version 0 and defaults to unaffected. Treat the narrative boundary cautiously and confirm against vendor or WPScan guidance. The available evidence attributes exploitation to missing handler authentication, an empty default key, and arbitrary file creation in a web-accessible location.
Mitigation direction
Update the plugin to version 5.37 or later after confirming current vendor guidance.
Disable or remove the plugin until it can be safely updated if immediate patching is impossible.
Prioritize internet-facing sites and default or incomplete plugin configurations.
Investigate exposed systems for unauthorized files and signs of server compromise.
Validation and detection
Inventory WordPress sites and record the installed FacturaONE plugin version.
Confirm no installation earlier than version 5.37 remains active.
Identify installations still using the default unconfigured cryptographic-key state.
Review web-accessible directories for unexpected or recently created executable files.
Check server and WordPress logs for suspicious requests to plugin handlers.
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.
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: noTechnical 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-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.