CVE-2026-102427: Ordasoft Joomla Cck remote code execution (CVSS 10.0)

Description

Joomla Extension - ordasoft.com - Unauthenticated Remote Code Execution in OrdaSoft Joomla CCK < 8.3.16 - site/uploader.php is reached through the component’s normal frontend routing (task=getContent), a task with no authentication or ACL check anywhere in the dispatch chain. The handler validates the uploaded file’s content with a real magic-byte MIME check, but the extension allow-list that would otherwise restrict the saved file’s extension was present in the source and commented out. The saved file’s extension was taken directly from the attacker-supplied filename with no validation, and the file was written to a path directly under the Joomla web root that is executed by the PHP handler. An image/PHP polyglot, a file whose header bytes satisfy the MIME check with PHP source appended after, passed the content check while carrying a .php extension of the attacker’s choosing.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

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

Affected products

Ordasoft Joomla Cck≥ 1.0.0 < 8.3.16

Remediation

Fixed in

Ordasoft Joomla Cck≥ 8.3.16

References

https://www.ordasoft.com/Product

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-102427 being actively exploited?

CVE-2026-102427 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.79%.

How severe is CVE-2026-102427?

CVE-2026-102427 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 0.79% probability of exploitation.

Which products are affected by CVE-2026-102427?

Affected products include Ordasoft Joomla Cck.

How do I fix CVE-2026-102427?

Upgrade affected software to a fixed version, for example Ordasoft Joomla Cck 8.3.16 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-102427 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo