{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-14159 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14159 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14159 is a medium-severity vulnerability in ays-pro Secure Copy Content Protection and Content Locking, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-14159 and fix it if it is affected.\n\nWhat it is: CVE-2025-14159 is a medium-severity vulnerability in ays-pro Secure Copy Content Protection and Content Locking, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-14159 in the wild and no public exploit code.\n\nAffected product: ays-pro Secure Copy Content Protection and Content Locking. 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-14159/ (Markdown: https://insights.sbomify.com/CVE-2025-14159/index.md)","id":"CVE-2025-14159","markdown":"https://insights.sbomify.com/CVE-2025-14159/index.md","name":"CVE-2025-14159","record":{"aliases":["GHSA-4x4p-8hj2-h92h"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can trick administrators into exporting sensitive user data via CSRF, exposing personal information in publicly accessible files.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Secure Copy Content Protection and Content Locking plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.9.2. This is due to missing nonce validation on the 'ays_sccp_results_export_file' AJAX action. This makes it possible for unauthenticated attackers to export sensitive plugin data including email addresses, IP addresses, physical addresses, user IDs, and other user information via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The exported data is stored in a publicly accessible file, allowing attackers to receive the sensitive information even though they are not authenticated.","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":"Secure Copy Content Protection and Content Locking \u003c= 4.9.2 - Cross-Site Request Forgery to Data Export","id":"CVE-2025-14159","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Upcoming for Calendly \u003c= 1.2.4 - Cross-Site Request Forgery to Settings Update","id":"CVE-2025-14160"},"packages":[],"prev":{"headline":"Coding Blocks \u003c= 1.1.0 - Cross-Site Request Forgery to Settings Update","id":"CVE-2025-14158"},"products":["Secure Copy Content Protection and Content Locking"],"published":"2025-12-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-04-08","vendors":["ays-pro"]},"summary":"Unauthenticated attackers can trick administrators into exporting sensitive user data via CSRF, exposing personal information in publicly accessible files.","url":"https://insights.sbomify.com/CVE-2025-14159/"}