Skip to content
Noroxi
CVE-2026-49287· NVD / CVE Program· CNA GitHub_M

Statamic CMS vulnerable to unsafe method invocation via collection sorting allows data destruction

Statamic is a Laravel and Git powered content management system (CMS). Prior to 5.73.23 and 6.20.0, the fix for CVE-2026-41175 was incomplete. It addressed the issue in the query builder, but the same protection was not applied to in-memory collection sorting. Manipulating sort parameters could result in the loss of content and assets. This requires a front-end template that passes request input into a tag's sort parameter. It is not exploitable by default — a template would need to be explicitly set up to sort by a visitor-controlled value. This has been fixed in 5.73.23 and 6.20.0.

HighCVSS 7.4 · v3.1—No exploit Fix available
Published
Jun 19, 2026
Updated
Jun 23, 2026
EPSS
0.5% · 37th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

29

Monitor

Low priority for now.

CVSS
29 / 40 · 7.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
7.4
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • statamic cms

    • < 5.73.23, >= 6.0.0, < 6.20.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagiststatamic/cmsfrom 6.0.0 · before 6.20.06.20.0
Packagiststatamic/cmsfrom 6.0.0-alpha.1 · before 6.13.06.13.0
Packagiststatamic/cmsbefore 5.73.205.73.20
Packagiststatamic/cmsbefore 5.73.235.73.23

Same product

statamic: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-64665Statamic: Account takeover via OAuth email matching without email-verification check
    32Monitor
  • CVE-2025-64112Statmatic vulnerable to Stored Cross-Site Scripting
    32Monitor
  • CVE-2026-64663Statamic: Unsafe method invocation via Antlers template resolution allows data destruction
    26Monitor
  • CVE-2026-64662Statamic: Missing authorization on navigation endpoint allows disclosure of restricted entries
    26Monitor
  • CVE-2026-71435Statamic: Stored Cross-Site Scripting in Automagic Form Notification Email Template
    24Monitor
  • CVE-2026-71293Statamic CMS Unguarded Exposure of 2FA Recovery Codes via Antlers current_user Variable
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
statamic cms5.73.23 · descriptionVendor (CNA)
Packagist:statamic/cms5.73.20Package registry (OSV)
Packagist:statamic/cms5.73.23Package registry (OSV)
Packagist:statamic/cms6.13.0Package registry (OSV)
Packagist:statamic/cms6.20.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-6466348 days apartStatamic: Unsafe method invocation via Antlers template resolution allows data destruction
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

Weakness class (CWE)

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

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records