LiveActive security incident?Get immediate response
CVE Record

CVE-2026-13051: Form::Processor::Field::HtmlArea versions from 0.06 through 1.162360 for Perl allow attacker selected method dispatch and resource exhaustion via an HTML::Tidy diagnostic that validate passes to add_error as a Locale::Maketext template

Form::Processor::Field::HtmlArea versions from 0.06 through 1.162360 for Perl allow attacker selected method dispatch and resource exhaustion via an HTML::Tidy diagnostic that validate passes to add_error as a Locale::Maketext template. validate runs HTML::Tidy over the submitted markup and passes each resulting message to add_error as its first argument, which add_error hands to the language handle as the Locale::Maketext message key. The default handle's lexicon sets `_AUTO`, so a message that is not a lexicon entry is compiled as a bracket notation template instead of being looked up. Tidy diagnostics quote the offending attribute name or value, so a bracket group in the submitted markup reaches the template position, where the first token of the group names a method called on the language handle and the remaining tokens are its arguments. A group such as `[0]` makes the compile croak, and neither the field nor the handle catches it, so the exception leaves validate. `[sprintf,%2000000000d,7]` reaches CORE::sprintf with an attacker chosen field width. One submission of crafted markup to an HtmlArea field throws an unhandled exception out of form validation or allocates an arbitrary amount of memory, and an application whose language handle subclass defines side effecting public methods makes those callable with attacker chosen arguments. The other field types pass fixed templates with the submitted value in an argument slot, where it stays inert, and are unaffected.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Applications using the affected Perl HtmlArea field may interpret attacker-controlled HTML validation errors as executable language templates. A remote, unauthenticated submission can trigger application errors, extreme memory consumption, or calls to public methods exposed by a custom language handler. Impact depends on application configuration and reachable HtmlArea forms.

Executive priority

Treat as an urgent remediation for internet-facing applications using HtmlArea. Prioritize asset discovery immediately, then patch or temporarily restrict affected inputs. Although active exploitation is not documented, unauthenticated remote reachability and potentially severe resource or method-dispatch consequences justify accelerated handling.

Technical view

HtmlArea passes HTML::Tidy diagnostics into add_error as Locale::Maketext message keys. With the default `_AUTO` lexicon behavior, attacker-influenced bracket notation in diagnostics is compiled as a template. This enables unhandled exceptions, attacker-selected method dispatch on the language handle, and potentially arbitrary memory allocation. Other field types are reported unaffected.

Likely exposure

Exposure requires Form::Processor::Field::HtmlArea versions 0.06 through 1.162360 and a reachable form accepting attacker-controlled markup. Applications using custom Locale::Maketext handle subclasses with side-effecting public methods may face greater integrity risk. The bundle does not identify specific deployed applications or confirm whether default configurations expose such forms.

Exploitation context

The supplied CVE record reports network-accessible, low-complexity, unauthenticated exploitation without user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation. Crafted submissions can disrupt validation or exhaust memory; additional effects depend on callable methods implemented by the application's language handle.

Researcher notes

The bundle names versions 0.06 through 1.162360 as affected and supplies a patch against 1.162360, but does not identify a fixed release. Its structured affected entry lists only 0.06 with default status unaffected, creating metadata ambiguity. Confirm exact version boundaries with maintainer guidance. No exploitation-in-the-wild evidence is supplied.

Mitigation direction

  • Apply the published MetaCPAN patch after compatibility testing.
  • Check current Form-Processor maintainer guidance for a fixed release.
  • Restrict or disable externally reachable HtmlArea inputs until remediation is complete.
  • Add resource limits and exception handling around form validation as defense in depth.

Validation and detection

  • Inventory installed Form-Processor versions across production and build environments.
  • Identify routes and workflows using Form::Processor::Field::HtmlArea.
  • Review language handle subclasses for public methods with side effects.
  • Confirm patched validation treats Tidy diagnostics as data, not templates.
  • Use safe regression tests in an isolated environment without resource-exhaustion inputs.
Prepared
Confidence
high
Sources
5

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 · low confidence lookup

CWE-1336: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
cwe · low confidence lookup

CWE-470: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-2026-13051 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.1 (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:N

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
3Timeline events
1ADP providers
5Source 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.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-13051Attack 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:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorForm-ProcessorForm-Processor, 0.06unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1336 · source CWE mapping

Improper Neutralization of Special Elements Used in a Template Engine

Improper Neutralization of Special Elements Used in a Template Engine represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-470 · source CWE mapping

Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.