{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-43747 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-43747 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-43747 is a medium-severity server-side request forgery vulnerability in Liferay Digital Experience Platform, published on 21 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-43747 and fix it if it is affected.\n\nWhat it is: CVE-2025-43747 is a medium-severity server-side request forgery vulnerability in Liferay Digital Experience Platform, published on 21 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-43747 in the wild and no public exploit code.\n\nAffected product: Liferay Digital Experience Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-43747/ (Markdown: https://insights.sbomify.com/CVE-2025-43747/index.md)","id":"CVE-2025-43747","markdown":"https://insights.sbomify.com/CVE-2025-43747/index.md","name":"CVE-2025-43747","record":{"aliases":["GHSA-7gq9-6fw6-w5q3"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Liferay DXP","requires_auth":"high_privilege","summary":"An attacker can bypass domain validation in Liferay DXP to perform server-side request forgery attacks, potentially accessing internal resources.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Liferay","cpe":[{"product":"digital_experience_platform","vendor":"liferay"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A server-side request forgery (SSRF) vulnerability exists in the Liferay DXP 2025.Q2.0 through 2025.Q2.3 due to insecure domain validation on analytics.cloud.domain.allowed, allowing an attacker to perform requests by change the domain and bypassing the validation method, this insecure validation is not distinguishing between trusted subdomains and malicious domains.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Server-side request forgery in DXP","id":"CVE-2025-43747","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"liferay:digital_experience_platform","products":["liferay:digital_experience_platform"],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Liferay Portal Vulnerable to Cross-Site Request Forgery","id":"CVE-2025-43748"},"packages":[],"prev":{"headline":"Liferay Portal Vulnerable to Cross-Site Scripting in Dynamic Data Mapping","id":"CVE-2025-43746"},"products":["DXP"],"published":"2025-08-21","related":[{"cvss_score":9.6,"headline":"Liferay Portal and Liferay DXP Vulnerable to CSRF in the Script Console","id":"CVE-2024-8980","kev_date_added":null,"published":"2024-10-22"},{"cvss_score":9.6,"headline":"Liferay Portal and Liferay DXP vulnerable to reflected Cross-site Scripting","id":"CVE-2023-42496","kev_date_added":null,"published":"2024-02-21"},{"cvss_score":9.6,"headline":"Liferay Portal Language Override edit screen and Liferay DXP vulnerable to reflected Cross-site Scripting","id":"CVE-2023-42498","kev_date_added":null,"published":"2024-02-21"},{"cvss_score":9.6,"headline":"Liferay Portal and Liferay DXP vulnerable to Cross-site Scripting","id":"CVE-2024-25147","kev_date_added":null,"published":"2024-02-21"},{"cvss_score":9.6,"headline":"Liferay Portal Frontend JS module's portlet.js and Liferay DXP vulnerable to Cross-site Scripting","id":"CVE-2024-26269","kev_date_added":null,"published":"2024-02-21"},{"cvss_score":9.6,"headline":"Liferay Portal stored cross-site scripting (XSS) vulnerability","id":"CVE-2024-25145","kev_date_added":null,"published":"2024-02-07"},{"cvss_score":9.6,"headline":"Liferay Portal and Liferay DXP Vulnerable to Reflected XSS via the Export for Translation Page","id":"CVE-2023-42497","kev_date_added":null,"published":"2023-10-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-21","vendors":["Liferay"]},"summary":"An attacker can bypass domain validation in Liferay DXP to perform server-side request forgery attacks, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2025-43747/"}