{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-1322 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-1322 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1322 is a medium-severity vulnerability in wppost WP-Recall – Registration, Profile, Commerce \u0026 More, published on 8 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-1322 and fix it if it is affected.\n\nWhat it is: CVE-2025-1322 is a medium-severity vulnerability in wppost WP-Recall – Registration, Profile, Commerce \u0026 More, published on 8 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-1322 in the wild and no public exploit code.\n\nAffected product: wppost WP-Recall – Registration, Profile, Commerce \u0026 More. 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-1322/ (Markdown: https://insights.sbomify.com/CVE-2025-1322/index.md)","id":"CVE-2025-1322","markdown":"https://insights.sbomify.com/CVE-2025-1322/index.md","name":"CVE-2025-1322","record":{"aliases":["GHSA-873c-2c5r-x992"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Unauthenticated attackers can view protected, private, or draft post content via the feed shortcode due to insufficient access restrictions.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp-recall","vendor":"plechevandrey"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The WP-Recall – Registration, Profile, Commerce \u0026 More plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 16.26.10 via the 'feed' shortcode due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to view data from password protected, private, or draft posts that they should not have access to.","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":"WP-Recall – Registration, Profile, Commerce \u0026 More \u003c= 16.26.10 - Authenticated (Contributor+) Protected Post Disclosure","id":"CVE-2025-1322","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"WP-Recall – Registration, Profile, Commerce \u0026 More \u003c= 16.26.10 - Unauthenticated SQL Injection","id":"CVE-2025-1323"},"packages":[],"prev":{"headline":"teachPress \u003c= 9.0.7 - Authenticated (Contributor+) SQL Injection","id":"CVE-2025-1321"},"products":["WP-Recall – Registration, Profile, Commerce \u0026 More"],"published":"2025-03-08","related":[{"cvss_score":9.8,"headline":"Auth bypass in WP-Recall – Registration, Profile, Commerce \u0026 More","id":"CVE-2024-8292","kev_date_added":null,"published":"2024-09-06"},{"cvss_score":7.5,"headline":"WP-Recall – Registration, Profile, Commerce \u0026 More \u003c= 16.26.10 - Unauthenticated SQL Injection","id":"CVE-2025-1323","kev_date_added":null,"published":"2025-03-08"},{"cvss_score":6.4,"headline":"Cross-site scripting in WP-Recall – Registration, Profile, Commerce \u0026 More","id":"CVE-2025-1324","kev_date_added":null,"published":"2025-03-08"},{"cvss_score":6.3,"headline":"Missing authorization in WP-Recall – Registration, Profile, Commerce \u0026 More","id":"CVE-2025-1325","kev_date_added":null,"published":"2025-03-08"},{"cvss_score":5.3,"headline":"WP-Recall – Registration, Profile, Commerce \u0026 More \u003c= 16.26.6 - Unauthenticated Payment Deletion via delete_payment","id":"CVE-2024-1175","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":4.7,"headline":"WP-Recall \u003c 16.26.12 - Admin+ SQL Injection","id":"CVE-2024-9770","kev_date_added":null,"published":"2025-03-25"}],"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":"2026-04-08","vendors":["wppost"]},"summary":"Unauthenticated attackers can view protected, private, or draft post content via the feed shortcode due to insufficient access restrictions.","url":"https://insights.sbomify.com/CVE-2025-1322/"}