dbcve.org
InjectionWeakness · CWE-74

CVE-2026-14749

HIGH · 7.3 CVSS v3.1 Published 2026-07-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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 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.

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

The vulnerability is a code injection flaw in the PHP application 'mjperpinosa stumasy' where user-supplied input to the 'mathematical_sentence' parameter in application/pages/imba_calculator/calculate.php is passed directly to PHP's eval() function without sanitization, allowing remote attackers to execute arbitrary PHP code.

MitigationReplace the unsafe eval() call with a secure mathematical expression parser library (such as Brick/Math or Laminas-Math) that does not execute arbitrary code, and implement strict input validation on the mathematical_sentence parameter.

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

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
Low
Integrity
Low
Availability
Low

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

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. Locate the vulnerable PHP file
    Search for the file calculate.php in the path application/pages/imba_calculator/ within your web root directory
    Affected if The file application/pages/imba_calculator/calculate.php exists in your environment
  2. Verify eval() usage with mathematical_sentence parameter
    Open the calculate.php file and search for the 'mathematical_sentence' parameter being passed to the eval() function. Look for code patterns like eval($_POST['mathematical_sentence']) or eval($_GET['mathematical_sentence'])
    Affected if The code shows mathematical_sentence parameter being directly passed to eval() without any sanitization function (such as preg_replace, intval, or a math parser)
  3. Confirm parameter input source
    Check if the mathematical_sentence parameter is received via $_GET, $_POST, or $_REQUEST and then immediately fed to eval()
    Affected if The parameter is received from user input (GET/POST) and reaches eval() without validation
  4. Check if the imba_calculator module is accessible
    Attempt to access the calculate.php endpoint via HTTP (e.g., curl or browser request to application/pages/imba_calculator/calculate.php) or verify the route configuration exposes this endpoint
    Affected if The calculate.php endpoint is accessible via HTTP/HTTPS requests and accepts the mathematical_sentence parameter
  5. Identify if application is running
    Check if the mjperpinosa stumasy PHP application is deployed and running on your web server
    Affected if The mjperpinosa stumasy application is installed and the imba_calculator functionality is enabled

You are affected if the mjperpinosa stumasy application is running, the file application/pages/imba_calculator/calculate.php exists, and the mathematical_sentence parameter is passed directly to PHP's eval() function without sanitization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace the unsafe eval() call with a secure mathematical expression parser library (such as Brick/Math or Laminas-Math) that does not execute arbitrary code, and implement strict input validation on the mathematical_sentence parameter.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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