Skip to main content
VulnerabilityPublished Updated

CVE-2026-14749: mjperpinosa stumasy · Code Injection

Affects mjperpinosa stumasySource CVE Database V5

0
Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
mjperpinosastumasyAffected
  • =327d1b0f2915ba79d7ef8ebb74553e987609d9be
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:mjperpinosa:stumasy:*:*:*:*:*:*:*:*

AI-suggested

Since the vendor has not responded or released a fix, users should monitor for official updates. In the meantime, restricting access to the vulnerable functionality or input validation to prevent code injection may reduce risk.

Description

A vulnerability was identified in mjperpinosa stumasy up to 327d1b0f2915ba79d7ef8ebb74553e987609d9be. Impacted is the function eval of the file application/pages/imba_calculator/calculate.php. The manipulation of the argument mathematical_sentence leads to code injection. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.

References

Community reviews

Loading reviews…