LiveActive security incident?Get immediate response
CVE Record

CVE-2021-26033: [20210502] - Core - CSRF in AJAX reordering endpoint

An issue was discovered in Joomla! 3.0.0 through 3.9.26. A missing token check causes a CSRF vulnerability in the AJAX reordering endpoint.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Joomla CMS versions 3.0.0 through 3.9.26 missed a CSRF token check in an AJAX reordering function. A malicious site could potentially cause a logged-in Joomla user to perform an unintended reorder action. The sources do not describe data theft, remote code execution, or active exploitation.

Executive priority

Treat this as a routine but necessary web-platform security update. It is not evidenced as actively exploited, but affected Joomla sites should be upgraded through normal vulnerability management before admin users are exposed to avoidable CSRF risk.

Technical view

CVE-2021-26033 is a CSRF issue in Joomla Core's AJAX reordering endpoint caused by a missing token check. The affected range is Joomla CMS 3.0.0 through 3.9.26. No CVSS score, CWE, exploit details, or named fixed version are present in the supplied bundle.

Likely exposure

Exposure is limited to Joomla CMS deployments in the affected 3.0.0-3.9.26 range, especially where privileged users access the administration interface from browsers that could be targeted with CSRF.

Exploitation context

The bundle does not report active exploitation, and KEV is false. CSRF generally depends on a logged-in victim interacting with attacker-controlled content, but the supplied sources do not provide attack prerequisites beyond the missing token check.

Researcher notes

Evidence is sparse: the bundle identifies the vulnerable component and affected range but lacks CVSS, CWE, fixed-version text, and exploit telemetry. Avoid assuming impact beyond unintended reordering unless the vendor advisory or local testing confirms it.

Mitigation direction

  • Identify Joomla CMS instances and compare versions against 3.0.0 through 3.9.26.
  • Review the Joomla vendor advisory for the official fixed or recommended upgrade path.
  • Prioritize updating affected Joomla installations to a vendor-supported non-affected release.
  • Reduce unnecessary administrative exposure while remediation is planned.
  • Remind administrators to avoid untrusted links while logged into Joomla.

Validation and detection

  • Confirm each Joomla CMS deployment version from trusted asset inventory or administration records.
  • Check whether any instance remains within Joomla 3.0.0 through 3.9.26.
  • Review vendor release notes to verify CSRF protection was addressed.
  • Look for unexpected content ordering changes in administrative audit trails, if available.
Prepared
Confidence
medium
Sources
3

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.

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-2021-26033 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Joomla! ProjectJoomla! CMS3.0.0-3.9.26Listed
Weakness

CWE details

No CWE listed

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