{"id":69317,"date":"2025-08-31T19:13:18","date_gmt":"2025-08-31T19:13:18","guid":{"rendered":""},"modified":"2025-10-02T00:14:52","modified_gmt":"2025-10-02T06:14:52","slug":"cve-2025-55368-unauthorized-supplier-status-modification-in-jsherp-v3-5","status":"publish","type":"post","link":"https:\/\/www.ameeba.com\/blog\/cve-2025-55368-unauthorized-supplier-status-modification-in-jsherp-v3-5\/","title":{"rendered":"<strong>CVE-2025-55368: Unauthorized Supplier Status Modification in jshERP v3.5<\/strong>"},"content":{"rendered":"<p><strong>Overview<\/strong><\/p>\n<p>In the realm of cybersecurity, the discovery of new vulnerabilities is a routine occurrence. However, when such vulnerabilities have the potential to compromise entire systems or leak sensitive data, they become a matter of paramount concern. CVE-2025-55368 is one such vulnerability, affecting jshERP v3.5, a popular enterprise resource planning software. This <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-53145-type-confusion-vulnerability-in-windows-message-queuing-allowing-remote-code-execution\/\"  data-wpil-monitor-id=\"78207\">vulnerability allows<\/a> unauthorized attackers the ability to arbitrarily modify supplier status under any account, thus presenting a significant risk to businesses relying on jshERP for their operations.<\/p>\n<p><strong>Vulnerability Summary<\/strong><\/p>\n<p>CVE ID: CVE-2025-55368<br \/>\nSeverity: High (CVSS 8.8)<br \/>\nAttack Vector: Network<br \/>\nPrivileges Required: None<br \/>\nUser Interaction: None<br \/>\nImpact: <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-8939-buffer-overflow-vulnerability-in-tenda-ac20-leading-to-potential-system-compromise\/\"  data-wpil-monitor-id=\"78308\">Potential system<\/a> compromise or data leakage<\/p>\n<p><strong>Affected Products<\/strong><\/p><div id=\"ameeb-3534407371\" class=\"ameeb-content-2 ameeb-entity-placement\"><div style=\"border-left: 4px solid #555; padding-left: 20px; margin: 48px 0; font-family: Roboto, sans-serif; color: #ffffff; line-height: 1.6; max-width: 700px;\">\r\n  <h2 style=\"margin-top: 0; font-size: 20px; font-weight: 600; display: flex; align-items: center;\">\r\n    <a href=\"https:\/\/www.ameeba.com\/chat\" style=\"display: inline-flex; align-items: center; margin-right: 8px;\">\r\n      <img decoding=\"async\" src=\"https:\/\/www.ameeba.com\/blog\/wp-content\/uploads\/2025\/10\/Best-App-icon-Ameeba.png\" alt=\"Ameeba Chat Icon\" style=\"width: 40px; height: 40px;\" \/>\r\n    <\/a>\r\n    A new way to communicate\r\n  <\/h2>\r\n\r\n  <p style=\"margin-bottom: 12px;\">\r\n    Ameeba Chat is built on encrypted identity, not personal profiles.\r\n  <\/p>\r\n\r\n  <p style=\"margin-bottom: 16px;\">\r\n    Message, call, share files, and coordinate with identities kept separate.\r\n  <\/p>\r\n\r\n  <ul style=\"list-style: none; padding-left: 0; margin-bottom: 20px;\">\r\n    <li>\u2022 Encrypted identity<\/li>\r\n    <li>\u2022 Ameeba Chat authenticates access<\/li>\r\n    <li>\u2022 Aliases and categories<\/li>\r\n    <li>\u2022 End-to-end encrypted chat, calls, and files<\/li>\r\n    <li>\u2022 Secure notes for sensitive information<\/li>\r\n  <\/ul>\r\n\r\n  <p style=\"font-style: italic; font-weight: 600; margin-bottom: 24px;\">\r\n    Private communication, rethought.\r\n  <\/p>\r\n\r\n  <div style=\"display: flex; flex-wrap: wrap; gap: 12px;\">\r\n    <a href=\"https:\/\/www.ameeba.com\/chat\/download\" style=\"background-color: #ffffff; color: #000000; padding: 10px 20px; text-decoration: none; border-radius: 6px; font-weight: 500;\">Download Ameeba Chat<\/a>\r\n    <a href=\"https:\/\/www.ameeba.com\/chat\" style=\"border: 1px solid #ffffff; color: #ffffff; padding: 10px 20px; text-decoration: none; border-radius: 6px; font-weight: 500;\">Learn More<\/a>\r\n  <\/div>\r\n<\/div>\r\n<\/div>\n<p>Product | Affected Versions<\/p>\n<p>jshERP  | v3.5<\/p>\n<p><strong>How the Exploit Works<\/strong><\/p>\n<p>The exploit takes advantage of the incorrect <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-47993-improper-access-control-vulnerability-in-microsoft-pc-manager\/\"  data-wpil-monitor-id=\"77519\">access control<\/a> in the component controllerRoleController.java of jshERP v3.5. This <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2011-10018-unauthorized-backdoor-in-mybb-1-6-4-allows-remote-code-execution\/\"  data-wpil-monitor-id=\"78791\">allows unauthorized<\/a> attackers to modify supplier status under any account without proper authorization. The attacker could send a specifically crafted HTTP request to manipulate the supplier status. A successful attack could <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-42950-sap-landscape-transformation-vulnerability-leading-to-potential-system-compromise\/\"  data-wpil-monitor-id=\"77584\">lead to a potential system<\/a> compromise or data leakage, depending on the attacker&#8217;s intent and capability.<\/p>\n<p><strong>Conceptual Example Code<\/strong><\/p><div id=\"ameeb-1239592264\" class=\"ameeb-content ameeb-entity-placement\"><div class=\"poptin-embedded\" data-id=\"f6b387694f681\"><\/div>\r\n\r\n\r\n\r\n\r\n\r\n<\/div>\n<p>The following is a<br \/>\n<strong>conceptual<\/strong><br \/>\n example of how the vulnerability might be exploited. This is a simplified HTTP request illustrating the potential attack:<\/p>\n<pre><code class=\"\" data-line=\"\">POST \/jshERP\/RoleController\/modifySupplierStatus HTTP\/1.1\nHost: target.example.com\nContent-Type: application\/json\n{ &quot;supplierId&quot;: &quot;1234&quot;, &quot;newStatus&quot;: &quot;Inactive&quot; }<\/code><\/pre>\n<p>In this example, the attacker is attempting to modify the status of a supplier with the ID &#8220;1234&#8221; to &#8220;Inactive&#8221;. This could disrupt the victim&#8217;s business operations or allow for further exploitations based on the changed supplier status.<\/p>\n<p><strong>Mitigation Guidance<\/strong><\/p>\n<p>The most effective <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-21120-trusting-http-permission-methods-on-the-server-side-vulnerability-in-dell-avamar\/\"  data-wpil-monitor-id=\"81531\">method to mitigate this vulnerability<\/a> is to apply the patch provided by the vendor. This patch rectifies the <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-50870-incorrect-access-control-vulnerability-in-institute-of-current-students-1-0\/\"  data-wpil-monitor-id=\"79316\">incorrect access control<\/a>, preventing unauthorized modification of supplier status. If the patch cannot be applied immediately, implementing a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can serve as a temporary mitigation, alerting administrators to <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2024-7457-macos-authorization-model-exploit-leading-to-potential-mitm-attacks\/\"  data-wpil-monitor-id=\"79966\">potential attacks and possibly preventing successful exploitation<\/a>. However, these measures are only temporary and do not <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-58280-object-heap-address-exposure-vulnerability-in-ark-ets\/\"  data-wpil-monitor-id=\"87325\">address the root cause of the vulnerability<\/a>. Therefore, applying the vendor\u2019s patch should be prioritized as soon as possible.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Overview In the realm of cybersecurity, the discovery of new vulnerabilities is a routine occurrence. However, when such vulnerabilities have the potential to compromise entire systems or leak sensitive data, they become a matter of paramount concern. CVE-2025-55368 is one such vulnerability, affecting jshERP v3.5, a popular enterprise resource planning software. This vulnerability allows unauthorized [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"footnotes":""},"categories":[1],"tags":[],"vendor":[],"product":[],"attack_vector":[],"asset_type":[],"severity":[],"exploit_status":[],"class_list":["post-69317","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts\/69317","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/comments?post=69317"}],"version-history":[{"count":9,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts\/69317\/revisions"}],"predecessor-version":[{"id":80155,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts\/69317\/revisions\/80155"}],"wp:attachment":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/media?parent=69317"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/categories?post=69317"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/tags?post=69317"},{"taxonomy":"vendor","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/vendor?post=69317"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/product?post=69317"},{"taxonomy":"attack_vector","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/attack_vector?post=69317"},{"taxonomy":"asset_type","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/asset_type?post=69317"},{"taxonomy":"severity","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/severity?post=69317"},{"taxonomy":"exploit_status","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/exploit_status?post=69317"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}