dbcve.org
Astroid FrameworkApplication · Templaza

CVE-2026-21628

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-05
Fix available
A fix is available. Upgrade to after 3.3.10 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A improperly secured file management feature allows uploads of dangerous data types for unauthenticated users, leading to remote code execution.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an unrestricted file upload vulnerability in a file management feature that lacks proper authentication and file type validation. Unauthenticated attackers can upload dangerous executable files (such as web shells, scripts, or binaries) to the server, leading to remote code execution.

MitigationImplement authentication requirements for the file upload feature and enforce strict allowlist-based file type validation (including content/MIME-type verification) with secure storage outside web root and appropriate file permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Astroid FrameworkApplication
Affected:>= 2.0.0, <= 3.3.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Templaza Astroid Framework is installed
    Access Joomla extension manager and confirm the Astroid Framework extension is listed as installed, or check the /administrator/components/com_astroid or /libraries/astroid directory exists on the server
    Affected if The extension is present in the Joomla installation
  2. Determine the installed Astroid Framework version
    Check the version.xml or version.php file within the Astroid Framework directory (commonly in /libraries/astroid/ or /administrator/components/com_astroid/), or view the extension details in Joomla's extension manager under the Libraries or Templates tab
    Affected if The version number falls within >= 2.0.0 and <= 3.3.10
  3. Confirm the file upload feature exists and is accessible
    Locate the file upload functionality in the Astroid admin panel (typically under Templates > Astroid Template Manager or a file manager section), and verify the endpoint is reachable without authentication requirements
    Affected if The upload endpoint responds without requiring login credentials
  4. Check upload directory location
    Examine the configuration or code defining where uploaded files are stored - verify if the upload path is within the webroot (public_html, www, or htdocs)
    Affected if Uploaded files are stored inside the web-accessible directory tree

If Astroid Framework versions 2.0.0 through 3.3.10 are installed and the unauthenticated file upload feature is accessible, the environment is vulnerable to remote code execution via malicious file uploads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.3.10
Interim mitigation

Implement authentication requirements for the file upload feature and enforce strict allowlist-based file type validation (including content/MIME-type verification) with secure storage outside web root and appropriate file permissions.

Recommended fix Moderate confidence

Astroid Framework 3.3.11 or later (latest stable release)

  1. 1. Backup your current Astroid Framework installation and database
  2. 2. Download the latest stable release of Astroid Framework from the official source (astroidframe.work)
  3. 3. Review the release notes for version 3.3.11 or later to understand included security fixes
  4. 4. Replace the existing framework files with the new version, preserving your configuration files
  5. 5. Verify the file upload functionality is now properly restricted - ensure uploaded files are validated for safe types and stored outside web-accessible directories
  6. 6. Test that authenticated users can still upload legitimate file types while unauthenticated uploads are blocked
  7. 7. Monitor for any unusual file uploads or RCE attempts
Caveat Review migration notes if upgrading across major versions; minor version upgrades within 3.x should have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Astroid Framework Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21628 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21628 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data