Jinher Oa
Monthly
We need to produce a JSON object with specific fields. Let's analyze the input carefully. Input: - CVE ID: CVE-2025-11341 - Description: "A security flaw has been discovered in Jinher OA up to 2.0. This affects an unknown function of the file /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx/?type=SystemUserInfo&style=1. Performing manipulation results in xml external entity reference. Remote exploitation of the attack is possible. The exploit has been released to the public and may be exploited." - CVSS Score: 5.5 (looks like a score, but vector is CVSS v4.0. I'll use that.) - CVSS Vector: 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - CWE: CWE-610 Externally Controlled Reference to a Resource in Another Sphere (probably XML External Entity) - EPSS Score: 0.03% (percentile 10%) - POC/Exploit: Publicly available - Reported by: cna@vuldb.com - CPE: cpe:2.3:a:jinher:jinher_oa:*:*:*:*:*:*:*:* (version up to 2.0) - Tags: XXE, Jinher Oa - References: three VulDB links, one GitHub issue. Potential for KEV? No mention of KEV in input, so not in KEV. So exploitation status: "publicly available exploit code exists" because POC/Exploit says publicly available, but no KEV confirmation. So "publicly available exploit code exists". We'll note that. Now fields: product_name: "Jinher OA" (up to 2.0). Product name is "Jinher OA". So "Jinher OA" (1-3 words). I'll just use "Jinher OA". summary: 2-3 sentence plain-language synthesis. Do not copy description. Start with impact verb and product. E.g. "XML External Entity (XXE) injection in Jinher OA up to version 2.0 allows unauthenticated remote attackers to read local files or perform server-side request forgery via crafted XML input to /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx". The description says "xml external entity reference", remote exploitation possible. Exploit publicly released. EPSS low. No KEV. So summary: "An XML External Entity (XXE) injection vulnerability in Jinher OA (up to version 2.0) allows unauthenticated attackers to exfiltrate local files or perform SSRF by sending crafted requests to /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx. Exploit code is publicly available, but EPSS suggests low exploitation probability." Actually EPSS 0.03% is very low, but exploit publicly available. So mention POC available. Start with "XML External Entity (XXE) injection in Jinher OA allows unauthenticated remote attackers to...". Yes. technical_context: Mention the underlying technology: Jinher OA is an office automation platform likely using ASP.NET (from the .aspx path). The vulnerability is CWE-610, XXE. The attack vector is remote, via HTTP request to a specific page. The CPE is cpe:2.3:a:jinher:jinher_oa:*:*:*:*:*:*:*:*, indicating all versions up to 2.0. The vulnerability arises from parsing untrusted XML with external entity processing enabled. The file path suggests a WebDesign.aspx page that processes XML. Use educational tone. risk_assessment: Use provided CVSS 4.0 vector: AV:N/AC:L/AT:N/PR:N/UI:N with impacts VC:L/VI:L/VA:L (confidentiality, integrity, availability all low). EPSS 0.03%, very low exploitation probability. No KEV. POC publicly available. CVSS score 5.5 (medium). So risk: low threat activity but easy attack, so moderate risk if exposed. Check conflicting signals: CVSS indicates network vector, unauthenticated, low impact. EPSS suggests rare active exploitation. So while exploit is available, it's not widely targeted. So risk is limited to specific exposed instances. No conflicting. affected_products: Write paragraph: "Jinher OA versions up to 2.0, as identified by CPE cpe:2.3:a:jinher:jinher_oa:*:*:*:*:*:*:*:*. The specific vulnerable endpoint is /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx?type=SystemUserInfo&style=1. Vendor advisory may be available from VulDB (links provided)." But we need to avoid bullet points, just narrative. So: "Jinher OA versions up to and including 2.0 are affected. The known vulnerable file is /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx with specific parameters. The vendor advisory is tracked by VulDB (https://vuldb.com/?id.327226)." remediation: No patch version given. No mention of fixed version. So we need to suggest compensating controls. Since no patch, recommend: "Upgrade to a version beyond 2.0 if available, or apply input validation to disable XML external entity processing. As an immediate mitigation, restrict network access to the vulnerable endpoint or implement a web application firewall (WAF) rule to block XXE payloads. Disabling DTD processing in the XML parser configuration, if possible, would prevent exploitation." No exact version, so say: "No vendor-released patch has been confirmed; mitigate by disabling XML external entity processing or restricting access to the vulnerable aspx page." We'll craft. exploit_scenario: Realistic attack: An attacker sends a specially crafted HTTP request to the vulnerable endpoint containing a malicious XML payload with an external entity that points to a local file (e.g., /etc/passwd) or an external server to exfiltrate data. Since no authentication is required (PR:N), remote unauthenticated exploitation is possible. POC available. exploitation_conditions: The CVSS vector shows AV:N, so network accessible. PR:N so no authentication needed? Vector says PR:N, so unauthenticated. UI:N, so no user interaction. No specific conditions in description beyond the endpoint URL. It says "Performing manipulation results in xml external entity reference." No mention of special configuration. So conditions: "No special conditions — remote unauthenticated exploitation against default configurations of Jinher OA up to 2.0, provided the /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx endpoint is accessible over the network." The file path is specific, so it must be accessible. No limiting factors like authentication, so it's wide open. So: "No authentication or user interaction is required; the vulnerable endpoint must be reachable over the network. The attack works with default configurations." That's enough. attack_chain: Follow kill chain: Remote attacker discovers vulnerable endpoint → Sends crafted XML request with external entity → XML parser processes entity, allowing file read or SSRF → Impact (Confidentiality/Integrity/Availability low). We'll use: "Send crafted HTTP POST request to vulnerable endpoint → XML parser resolves external entity → Exfiltrate sensitive file contents or perform SSRF". Steps: Access → Delivery (HTTP request with XML) → Exploit (XXE) → Execution (entity resolution) → Impact (file read/SSRF). I'll construct a chain of 4 steps: "Send crafted XML payload to WebDesign.aspx → Trigger XML external entity processing → Access arbitrary local files via entity resolution → Use exfiltrated data or trigger SSRF for further access". That's 4. Good. confidence_notes: We know exploit code is publicly available (GitHub issue referenced). The CVSS vector provided is from VulDB likely, but NVD hasn't published yet? The CVE is from VulDB. NVD references include the GitHub link as exploit. No vendor confirmation, just VulDB report. So: "Exploit code confirmed publicly available via GitHub. Affected product and version range confirmed by CPE from VulDB. No official vendor advisory or patch identified; patch status unknown. CVSS vector from VulDB indicates network-accessible, unauthenticated attack with low impact." We'll state what's missing. prevalence: Jinher OA is an office automation platform, likely Chinese product. How widely deployed? I'm not sure. It might be niche. I'll estimate low or medium? I'm leaning low because it's not a globally known product. Possibly used in some Chinese enterprises. I'll go with "low" and basis: "niche Chinese OA platform, limited enterprise deployment". Might be unknown but I'll pick low. prevalence_basis: "niche Chinese OA platform, limited global footprint." That's within 12 words. assessed_cvss_vector: We're supposed to provide our own CVSS 3.1 vector, not copy the given 4.0 one. Given the description: remote, unauthenticated, XXE. Attack vector: Network (AV:N). Attack Complexity: Low (AC:L) because just sending crafted request. Privileges Required: None (PR:N) because no authentication mentioned. User Interaction: None (UI:N) because no user involved. Scope: Unchanged? XXE can sometimes lead to scope change if exfiltrating data from a different system, but typically file read is on the same system, so Scope U. Confidentiality Impact: Low (C:L) as described in VC:L. Integrity Impact: Low (I:L). Availability Impact: Low (A:L). So vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. That's consistent. I'll output that as my assessed CVSS 3.1 vector. assessed_cvss_rationale: "Remote network exploitation without authentication or user interaction, with low confidentiality, integrity, and availability impacts from file read and SSRF." assessed_cvss40_vector: They already gave one, but I'll produce my own assessment consistent with the 3.1 vector. For 4.0: AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N. I'll use that. Now assemble JSON. Ensure all fields are strings. No arrays, no nesting. Use double quotes. Make sure the summary does not say "A vulnerability..." but start with "XML External Entity (XXE) injection in Jinher OA...". Yes. technical_context: mention CWE-610 and that it's an XML parsing issue with external entity processing. Use CPE to point to affected product. "The vulnerability is an XML External Entity injection (CWE-610) in the Jinher OA web application, which likely uses an ASP.NET XML parser that defaults to enabling external entity resolution. The vulnerable endpoint processes user-supplied XML in a POST request, and by crafting a malicious XML document with an external entity pointing to a local file or internal resource, an attacker can read sensitive files or initiate SSRF. The CPE cpe:2.3:a:jinher:jinher_oa:*:*:*:*:*:*:*:* captures all versions up to 2.0." risk_assessment: "CVSS 4.0 scores this as 5.5 Medium, with network attack vector, low complexity, no privileges or user interaction required, and low impact on all three CIA metrics. The EPSS estimate of 0.03% suggests very low likelihood of active exploitation in the wild, despite the public availability of exploit code. No CISA KEV entry indicates no known active exploitation campaigns. Overall, this is a straightforward XXE vulnerability but with limited post-exploitation impact, making it a moderate priority for organizations using the affected product." affected_products: "Jinher OA versions up to and including 2.0, identified by CPE cpe:2.3:a:jinher:jinher_oa:*:*:*:*:*:*:*:*. The vulnerability is located in the /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx endpoint with specific parameters. The report is available at VulDB (https://vuldb.com/?id.327226)." remediation: "Apply the vendor patch if available (no specific version identified in the advisory). As a workaround, disable XML external entity processing in the application's XML parser configuration, or restrict network access to the vulnerable .aspx file using a WAF or firewall rules. Disabling DTD resolution entirely may break legitimate functionality if required by the application; test thoroughly before deploying." exploit_scenario: "An unauthenticated remote attacker sends a specially crafted HTTP POST request to the vulnerable /c6/Jhsoft.Web
A vulnerability was determined in Jinher OA 2.0. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A security flaw has been discovered in Jinher OA 2.0. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A vulnerability was found in Jinher OA up to 1.2. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A vulnerability has been found in Jinher OA up to 1.2. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A flaw has been found in Jinher OA up to 1.2. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A vulnerability was detected in Jinher OA 1.0. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A vulnerability has been found in Jinher OA 1.0.aspx. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
XML External Entity (XXE) processing vulnerability in Jinher OA 1.1 allows unauthenticated remote attackers to read local files or perform server-side request forgery via the XmlHttp.aspx endpoint. Public exploit code is available, though no active exploitation has been reported and EPSS indicates low exploitation probability.
XML External Entity (XXE) injection in Jinher OA 1.2 allows unauthenticated remote attackers to read arbitrary files and potentially exfiltrate data via the ProjectScheduleDelete.aspx endpoint. Exploit code is publicly available, but the EPSS exploitation probability remains low (0.07%) and the vulnerability is not known to be actively exploited.
CVE-2025-7523 is an XML External Entity (XXE) injection vulnerability in Jinher OA 1.0 affecting the /c6/Jhsoft.Web.message/ToolBar/DelTemp.aspx endpoint. An unauthenticated remote attacker can exploit this to read sensitive files, modify data, or cause denial of service with low attack complexity. The vulnerability has been publicly disclosed with exploit code available, increasing real-world exploitation risk.
We need to produce a JSON object with specific fields. Let's analyze the input carefully. Input: - CVE ID: CVE-2025-11341 - Description: "A security flaw has been discovered in Jinher OA up to 2.0. This affects an unknown function of the file /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx/?type=SystemUserInfo&style=1. Performing manipulation results in xml external entity reference. Remote exploitation of the attack is possible. The exploit has been released to the public and may be exploited." - CVSS Score: 5.5 (looks like a score, but vector is CVSS v4.0. I'll use that.) - CVSS Vector: 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - CWE: CWE-610 Externally Controlled Reference to a Resource in Another Sphere (probably XML External Entity) - EPSS Score: 0.03% (percentile 10%) - POC/Exploit: Publicly available - Reported by: cna@vuldb.com - CPE: cpe:2.3:a:jinher:jinher_oa:*:*:*:*:*:*:*:* (version up to 2.0) - Tags: XXE, Jinher Oa - References: three VulDB links, one GitHub issue. Potential for KEV? No mention of KEV in input, so not in KEV. So exploitation status: "publicly available exploit code exists" because POC/Exploit says publicly available, but no KEV confirmation. So "publicly available exploit code exists". We'll note that. Now fields: product_name: "Jinher OA" (up to 2.0). Product name is "Jinher OA". So "Jinher OA" (1-3 words). I'll just use "Jinher OA". summary: 2-3 sentence plain-language synthesis. Do not copy description. Start with impact verb and product. E.g. "XML External Entity (XXE) injection in Jinher OA up to version 2.0 allows unauthenticated remote attackers to read local files or perform server-side request forgery via crafted XML input to /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx". The description says "xml external entity reference", remote exploitation possible. Exploit publicly released. EPSS low. No KEV. So summary: "An XML External Entity (XXE) injection vulnerability in Jinher OA (up to version 2.0) allows unauthenticated attackers to exfiltrate local files or perform SSRF by sending crafted requests to /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx. Exploit code is publicly available, but EPSS suggests low exploitation probability." Actually EPSS 0.03% is very low, but exploit publicly available. So mention POC available. Start with "XML External Entity (XXE) injection in Jinher OA allows unauthenticated remote attackers to...". Yes. technical_context: Mention the underlying technology: Jinher OA is an office automation platform likely using ASP.NET (from the .aspx path). The vulnerability is CWE-610, XXE. The attack vector is remote, via HTTP request to a specific page. The CPE is cpe:2.3:a:jinher:jinher_oa:*:*:*:*:*:*:*:*, indicating all versions up to 2.0. The vulnerability arises from parsing untrusted XML with external entity processing enabled. The file path suggests a WebDesign.aspx page that processes XML. Use educational tone. risk_assessment: Use provided CVSS 4.0 vector: AV:N/AC:L/AT:N/PR:N/UI:N with impacts VC:L/VI:L/VA:L (confidentiality, integrity, availability all low). EPSS 0.03%, very low exploitation probability. No KEV. POC publicly available. CVSS score 5.5 (medium). So risk: low threat activity but easy attack, so moderate risk if exposed. Check conflicting signals: CVSS indicates network vector, unauthenticated, low impact. EPSS suggests rare active exploitation. So while exploit is available, it's not widely targeted. So risk is limited to specific exposed instances. No conflicting. affected_products: Write paragraph: "Jinher OA versions up to 2.0, as identified by CPE cpe:2.3:a:jinher:jinher_oa:*:*:*:*:*:*:*:*. The specific vulnerable endpoint is /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx?type=SystemUserInfo&style=1. Vendor advisory may be available from VulDB (links provided)." But we need to avoid bullet points, just narrative. So: "Jinher OA versions up to and including 2.0 are affected. The known vulnerable file is /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx with specific parameters. The vendor advisory is tracked by VulDB (https://vuldb.com/?id.327226)." remediation: No patch version given. No mention of fixed version. So we need to suggest compensating controls. Since no patch, recommend: "Upgrade to a version beyond 2.0 if available, or apply input validation to disable XML external entity processing. As an immediate mitigation, restrict network access to the vulnerable endpoint or implement a web application firewall (WAF) rule to block XXE payloads. Disabling DTD processing in the XML parser configuration, if possible, would prevent exploitation." No exact version, so say: "No vendor-released patch has been confirmed; mitigate by disabling XML external entity processing or restricting access to the vulnerable aspx page." We'll craft. exploit_scenario: Realistic attack: An attacker sends a specially crafted HTTP request to the vulnerable endpoint containing a malicious XML payload with an external entity that points to a local file (e.g., /etc/passwd) or an external server to exfiltrate data. Since no authentication is required (PR:N), remote unauthenticated exploitation is possible. POC available. exploitation_conditions: The CVSS vector shows AV:N, so network accessible. PR:N so no authentication needed? Vector says PR:N, so unauthenticated. UI:N, so no user interaction. No specific conditions in description beyond the endpoint URL. It says "Performing manipulation results in xml external entity reference." No mention of special configuration. So conditions: "No special conditions — remote unauthenticated exploitation against default configurations of Jinher OA up to 2.0, provided the /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx endpoint is accessible over the network." The file path is specific, so it must be accessible. No limiting factors like authentication, so it's wide open. So: "No authentication or user interaction is required; the vulnerable endpoint must be reachable over the network. The attack works with default configurations." That's enough. attack_chain: Follow kill chain: Remote attacker discovers vulnerable endpoint → Sends crafted XML request with external entity → XML parser processes entity, allowing file read or SSRF → Impact (Confidentiality/Integrity/Availability low). We'll use: "Send crafted HTTP POST request to vulnerable endpoint → XML parser resolves external entity → Exfiltrate sensitive file contents or perform SSRF". Steps: Access → Delivery (HTTP request with XML) → Exploit (XXE) → Execution (entity resolution) → Impact (file read/SSRF). I'll construct a chain of 4 steps: "Send crafted XML payload to WebDesign.aspx → Trigger XML external entity processing → Access arbitrary local files via entity resolution → Use exfiltrated data or trigger SSRF for further access". That's 4. Good. confidence_notes: We know exploit code is publicly available (GitHub issue referenced). The CVSS vector provided is from VulDB likely, but NVD hasn't published yet? The CVE is from VulDB. NVD references include the GitHub link as exploit. No vendor confirmation, just VulDB report. So: "Exploit code confirmed publicly available via GitHub. Affected product and version range confirmed by CPE from VulDB. No official vendor advisory or patch identified; patch status unknown. CVSS vector from VulDB indicates network-accessible, unauthenticated attack with low impact." We'll state what's missing. prevalence: Jinher OA is an office automation platform, likely Chinese product. How widely deployed? I'm not sure. It might be niche. I'll estimate low or medium? I'm leaning low because it's not a globally known product. Possibly used in some Chinese enterprises. I'll go with "low" and basis: "niche Chinese OA platform, limited enterprise deployment". Might be unknown but I'll pick low. prevalence_basis: "niche Chinese OA platform, limited global footprint." That's within 12 words. assessed_cvss_vector: We're supposed to provide our own CVSS 3.1 vector, not copy the given 4.0 one. Given the description: remote, unauthenticated, XXE. Attack vector: Network (AV:N). Attack Complexity: Low (AC:L) because just sending crafted request. Privileges Required: None (PR:N) because no authentication mentioned. User Interaction: None (UI:N) because no user involved. Scope: Unchanged? XXE can sometimes lead to scope change if exfiltrating data from a different system, but typically file read is on the same system, so Scope U. Confidentiality Impact: Low (C:L) as described in VC:L. Integrity Impact: Low (I:L). Availability Impact: Low (A:L). So vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. That's consistent. I'll output that as my assessed CVSS 3.1 vector. assessed_cvss_rationale: "Remote network exploitation without authentication or user interaction, with low confidentiality, integrity, and availability impacts from file read and SSRF." assessed_cvss40_vector: They already gave one, but I'll produce my own assessment consistent with the 3.1 vector. For 4.0: AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N. I'll use that. Now assemble JSON. Ensure all fields are strings. No arrays, no nesting. Use double quotes. Make sure the summary does not say "A vulnerability..." but start with "XML External Entity (XXE) injection in Jinher OA...". Yes. technical_context: mention CWE-610 and that it's an XML parsing issue with external entity processing. Use CPE to point to affected product. "The vulnerability is an XML External Entity injection (CWE-610) in the Jinher OA web application, which likely uses an ASP.NET XML parser that defaults to enabling external entity resolution. The vulnerable endpoint processes user-supplied XML in a POST request, and by crafting a malicious XML document with an external entity pointing to a local file or internal resource, an attacker can read sensitive files or initiate SSRF. The CPE cpe:2.3:a:jinher:jinher_oa:*:*:*:*:*:*:*:* captures all versions up to 2.0." risk_assessment: "CVSS 4.0 scores this as 5.5 Medium, with network attack vector, low complexity, no privileges or user interaction required, and low impact on all three CIA metrics. The EPSS estimate of 0.03% suggests very low likelihood of active exploitation in the wild, despite the public availability of exploit code. No CISA KEV entry indicates no known active exploitation campaigns. Overall, this is a straightforward XXE vulnerability but with limited post-exploitation impact, making it a moderate priority for organizations using the affected product." affected_products: "Jinher OA versions up to and including 2.0, identified by CPE cpe:2.3:a:jinher:jinher_oa:*:*:*:*:*:*:*:*. The vulnerability is located in the /c6/Jhsoft.Web.module/eformaspx/WebDesign.aspx endpoint with specific parameters. The report is available at VulDB (https://vuldb.com/?id.327226)." remediation: "Apply the vendor patch if available (no specific version identified in the advisory). As a workaround, disable XML external entity processing in the application's XML parser configuration, or restrict network access to the vulnerable .aspx file using a WAF or firewall rules. Disabling DTD resolution entirely may break legitimate functionality if required by the application; test thoroughly before deploying." exploit_scenario: "An unauthenticated remote attacker sends a specially crafted HTTP POST request to the vulnerable /c6/Jhsoft.Web
A vulnerability was determined in Jinher OA 2.0. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A security flaw has been discovered in Jinher OA 2.0. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A vulnerability was found in Jinher OA up to 1.2. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A vulnerability has been found in Jinher OA up to 1.2. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A flaw has been found in Jinher OA up to 1.2. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A vulnerability was detected in Jinher OA 1.0. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A vulnerability has been found in Jinher OA 1.0.aspx. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
XML External Entity (XXE) processing vulnerability in Jinher OA 1.1 allows unauthenticated remote attackers to read local files or perform server-side request forgery via the XmlHttp.aspx endpoint. Public exploit code is available, though no active exploitation has been reported and EPSS indicates low exploitation probability.
XML External Entity (XXE) injection in Jinher OA 1.2 allows unauthenticated remote attackers to read arbitrary files and potentially exfiltrate data via the ProjectScheduleDelete.aspx endpoint. Exploit code is publicly available, but the EPSS exploitation probability remains low (0.07%) and the vulnerability is not known to be actively exploited.
CVE-2025-7523 is an XML External Entity (XXE) injection vulnerability in Jinher OA 1.0 affecting the /c6/Jhsoft.Web.message/ToolBar/DelTemp.aspx endpoint. An unauthenticated remote attacker can exploit this to read sensitive files, modify data, or cause denial of service with low attack complexity. The vulnerability has been publicly disclosed with exploit code available, increasing real-world exploitation risk.