{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-13818 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-13818 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-13818 is a medium-severity vulnerability in genetechproducts Pie Register – User Registration, Profiles \u0026 Content Restriction, published on 21 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-13818 and fix it if it is affected.\n\nWhat it is: CVE-2024-13818 is a medium-severity vulnerability in genetechproducts Pie Register – User Registration, Profiles \u0026 Content Restriction, published on 21 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-13818 in the wild and no public exploit code.\n\nAffected product: genetechproducts Pie Register – User Registration, Profiles \u0026 Content Restriction. 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-2024-13818/ (Markdown: https://insights.sbomify.com/CVE-2024-13818/index.md)","id":"CVE-2024-13818","markdown":"https://insights.sbomify.com/CVE-2024-13818/index.md","name":"CVE-2024-13818","record":{"aliases":["GHSA-vq4p-pj29-ggrf"],"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 view sensitive user information via publicly exposed log files in the Registration Forms WordPress plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"pie_register","vendor":"genetechsolutions"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"The Registration Forms – User Registration Forms, Invitation-Based Registrations, Front-end User Profile, Login Form \u0026 Content Restriction plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.8.4 through publicly exposed log files. This makes it possible for unauthenticated attackers to view potentially sensitive information about users contained in the exposed log files.","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":"Information disclosure in Pie Register – User Registration, Profiles \u0026 Content Restriction","id":"CVE-2024-13818","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Melhor Envio \u003c= 2.15.11 - Unauthenticated Sensitive Information Exposure via Hardcoded Hash","id":"CVE-2024-13820"},"packages":[],"prev":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2024-13817"},"products":["Pie Register – User Registration, Profiles \u0026 Content Restriction"],"published":"2025-02-21","related":[{"cvss_score":10,"headline":"WordPress Pie Register plugin \u003c= 3.8.3.1 - Unauthenticated Arbitrary File Upload vulnerability","id":"CVE-2024-27957","kev_date_added":null,"published":"2024-03-17"},{"cvss_score":9.8,"headline":"Pie Register \u003c 3.7.1.6 - Unauthenticated SQL Injection","id":"CVE-2021-24731","kev_date_added":null,"published":"2021-11-08"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-15659","kev_date_added":null,"published":"2019-08-27"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-10969","kev_date_added":null,"published":"2018-06-17"},{"cvss_score":8.1,"headline":"Pie Register \u003c 3.7.1.6 - Unauthenticated Arbitrary Login","id":"CVE-2021-24647","kev_date_added":null,"published":"2021-11-08"},{"cvss_score":6.5,"headline":"Pie Register \u003c 3.8.1.3 - Unauthenticated Arbitrary User Deletion","id":"CVE-2022-4024","kev_date_added":null,"published":"2022-12-19"},{"cvss_score":6.5,"headline":"SQL injection in n/a","id":"CVE-2015-7682","kev_date_added":null,"published":"2015-10-16"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["genetechproducts"]},"summary":"Unauthenticated attackers can view sensitive user information via publicly exposed log files in the Registration Forms WordPress plugin.","url":"https://insights.sbomify.com/CVE-2024-13818/"}