dbcve.org
EasydiscussApplication · Stackideas

CVE-2026-21626

HIGH · 7.5 CVSS v3.1 Published 2026-02-06
Fix available
A fix is available. Upgrade to after 5.0.15 or later.
See remediation →
84/100
Remediation priority · High
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
Access control settings for forum post custom fields are not applied to the JSON output type, leading to an ACL violation vector an information disclosure

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 · moderate confidence

Forum post custom fields have access control list (ACL) settings that are intended to restrict visibility based on user permissions. However, when the data is requested via the JSON output type/API endpoint, these ACL checks are bypassed, allowing unauthorized users to retrieve sensitive custom field data through an information disclosure vulnerability.

MitigationApply the existing ACL permission checks to all output types, including JSON, when rendering forum post custom fields. Verify that unauthenticated or unauthorized users cannot access restricted custom field data through any output format.

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
EasydiscussApplication
Affected:>= 1.0.0, <= 5.0.15

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
None
Availability
None

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

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. Check installed Easydiscuss version
    Locate the Easydiscuss component version in your Joomla admin under Components > Easydiscuss, or check the version manifest file in the Easydiscuss installation directory
    Affected if Installed version is between 1.0.0 and 5.0.15 inclusive (any version in this range is affected)
  2. Verify custom fields are configured
    In Joomla admin, navigate to Components > Easydiscuss > Custom Fields and review whether any custom field definitions exist for forum posts
    Affected if Custom fields are created and assigned visibility restrictions for forum posts
  3. Identify JSON API endpoint usage
    Check if your site or any integrated applications query forum post data via JSON format (index.php?option=com_easydiscuss&format=json or API endpoints)
    Affected if JSON/API output type is used to retrieve forum post data
  4. Test JSON response for custom field disclosure
    Make a request to the JSON API endpoint for a forum post as an unauthenticated or low-privilege user and inspect whether restricted custom field data appears in the response
    Affected if JSON response contains custom field values that should be hidden based on ACL settings

If Easydiscuss version 1.0.0-5.0.15 is installed with custom fields configured and the JSON API exposes restricted custom field data to unauthorized users, the environment is affected by this vulnerability.

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 5.0.15
Interim mitigation

Apply the existing ACL permission checks to all output types, including JSON, when rendering forum post custom fields. Verify that unauthenticated or unauthorized users cannot access restricted custom field data through any output format.

Recommended fix Moderate confidence

Easydiscuss 5.0.16 or latest stable version

  1. 1. Visit stackideas.com and navigate to the Easydiscuss downloads/changelog section
  2. 2. Look for version 5.0.16 or later which should contain the security fix for the ACL bypass in JSON output type
  3. 3. Download and install the latest stable version of Easydiscuss (5.0.16 or later)
  4. 4. After upgrade, verify that the custom fields access controls are properly enforced for JSON output types
  5. 5. Test that non-privileged users can no longer access restricted custom field data through JSON endpoints
Caveat Review changelog for any breaking changes between 5.0.15 and the target upgrade version

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

Fix this in Easydiscuss Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21626 — 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-21626 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