Quick answers
- Is CVE-2026-14751 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14751 being exploited in the wild.
- How severe is CVE-2026-14751?
- Medium severity, with a CVSS score of 6.3, published 5 July 2026.
- Which products and versions are affected?
- Mjperpinosa Stumasy up to 327d1b0f2915ba79d7ef8ebb74553e987609d9be.
- Is there a fix for CVE-2026-14751?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-14751 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-14751?
- Check whether you run Mjperpinosa Stumasy at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A SQL injection vulnerability exists in mjperpinosa stumasy up to commit 327d1b0f2915ba79d7ef8ebb74553e987609d9be. The flaw is located in the `Notes_controller::search_scratch_data` function within `application/PHP/objects/notes/search_scratch_data.php`. The application fails to validate or allowlist the `field_name` POST parameter before concatenating it into a SQL query. While the `value` parameter is handled via prepared statements, the `field_name` identifier is treated as trusted syntax. An authenticated remote attacker can exploit this to perform time-based blind SQL injection, allowing for the exfiltration of database contents. As of the advisory date, no official patch has been released by the maintainer.
Affected products
- mjperpinosa stumasy up to 327d1b0f2915ba79d7ef8ebb74553e987609d9be
Timeline
- 2026-06-05: disclosed: Issue reported on GitHub repository
- 2026-07-05: advisory: CVE published to NVD