{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-0833 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-0833 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-0833 is a medium-severity missing authorization vulnerability in Unknown Church Admin, published on 28 Mar 2022. 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-2022-0833 and fix it if it is affected.\n\nWhat it is: CVE-2022-0833 is a medium-severity missing authorization vulnerability in Unknown Church Admin, published on 28 Mar 2022. 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-2022-0833 in the wild and no public exploit code.\n\nAffected product: Unknown Church Admin. 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-2022-0833/ (Markdown: https://insights.sbomify.com/CVE-2022-0833/index.md)","id":"CVE-2022-0833","markdown":"https://insights.sbomify.com/CVE-2022-0833/index.md","name":"CVE-2022-0833","record":{"aliases":["GHSA-9vf6-r8jp-w3m7"],"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 download database backups by exploiting missing authorization and CSRF checks in the Church Admin WordPress plugin.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"church_admin","vendor":"church_admin_project"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","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-862","name":"Missing Authorization"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Church Admin WordPress plugin before 3.4.135 does not have authorisation and CSRF in some of its action as well as requested files, allowing unauthenticated attackers to repeatedly request the \"refresh-backup\" action, and simultaneously keep requesting a publicly accessible temporary file generated by the plugin in order to disclose the final backup filename, which can then be fetched by the attacker to download the backup of the plugin's DB data","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":"Church Admin \u003c 3.4.135 - Unauthenticated Plugin's Backup Disclosure","id":"CVE-2022-0833","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Amelia \u003c= 1.0.46 - Stored Cross Site Scripting via lastName","id":"CVE-2022-0834"},"packages":[],"prev":{"headline":"Cross-site Scripting (XSS) - Stored in pimcore/pimcore","id":"CVE-2022-0832"},"products":["Church Admin"],"published":"2022-03-28","related":[{"cvss_score":9.9,"headline":"WordPress Church Admin plugin \u003c= 4.4.6 - Arbitrary File Upload vulnerability","id":"CVE-2024-37418","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":9.9,"headline":"WordPress Church Admin plugin \u003c= 4.1.5 - Arbitrary File Upload vulnerability","id":"CVE-2024-31280","kev_date_added":null,"published":"2024-04-07"},{"cvss_score":8.5,"headline":"WordPress Church Admin plugin \u003c= 4.0.27 - SQL Injection via shortcode vulnerability","id":"CVE-2024-30244","kev_date_added":null,"published":"2024-03-28"},{"cvss_score":7.1,"headline":"WordPress Church Admin Plugin \u003c= 3.7.29 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-34021","kev_date_added":null,"published":"2023-06-23"},{"cvss_score":6.5,"headline":"WordPress Church Admin plugin \u003c= 4.4.4 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-35764","kev_date_added":null,"published":"2024-06-21"},{"cvss_score":6.5,"headline":"WordPress Church Admin plugin \u003c= 4.1.17 - Stored Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-30193","kev_date_added":null,"published":"2024-03-27"},{"cvss_score":6.5,"headline":"WordPress Church Admin plugin \u003c= 4.0.26 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-30197","kev_date_added":null,"published":"2024-03-27"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Unknown"]},"summary":"Unauthenticated attackers can download database backups by exploiting missing authorization and CSRF checks in the Church Admin WordPress plugin.","url":"https://insights.sbomify.com/CVE-2022-0833/"}