{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-1051 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-1051 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-1051 is a medium-severity cross-site scripting vulnerability in Unknown WPQA Builder Plugin, published on 16 May 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-1051 and fix it if it is affected.\n\nWhat it is: CVE-2022-1051 is a medium-severity cross-site scripting vulnerability in Unknown WPQA Builder Plugin, published on 16 May 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-1051 in the wild and no public exploit code.\n\nAffected product: Unknown WPQA Builder Plugin. 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-1051/ (Markdown: https://insights.sbomify.com/CVE-2022-1051/index.md)","id":"CVE-2022-1051","markdown":"https://insights.sbomify.com/CVE-2022-1051/index.md","name":"CVE-2022-1051","record":{"aliases":["GHSA-p462-hx7j-6485"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated users can inject malicious scripts via profile fields in WPQA Builder, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wpqa_builder","vendor":"2code"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The WPQA Builder Plugin WordPress plugin before 5.2, used as a companion plugin for the Discy and Himer , does not sanitise and escape the city, phone or profile credentials fields when outputting it in the profile page, allowing any authenticated user to perform Cross-Site Scripting attacks.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-05-13","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-05-13T06:50:25Z","kind":"github_poc","ref":"https://github.com/V35HR4J/CVE-2022-1051","stars":2,"title":"WPQA \u003c 5.2 - Subscriber+ Stored Cross-Site Scripting via Profile fields"}],"tier":"poc_unverified"},"has_fix":null,"headline":"WPQA \u003c 5.2 - Subscriber+ Stored Cross-Site Scripting via Profile fields","id":"CVE-2022-1051","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Heap Buffer Overflow in iterate_chained_fixups in radareorg/radare2","id":"CVE-2022-1052"},"packages":[],"prev":{"headline":"Use after free in QEMU","id":"CVE-2022-1050"},"products":["WPQA Builder Plugin"],"published":"2022-05-16","related":[{"cvss_score":8.8,"headline":"WPQA \u003c 6.1.1 - Arbitrary Category and Tag Follow/Unfollow via CSRF","id":"CVE-2024-2376","kev_date_added":null,"published":"2024-07-03"},{"cvss_score":8.8,"headline":"WPQA \u003c 5.9 - Follow/Unfollow via CSRF","id":"CVE-2022-3688","kev_date_added":null,"published":"2022-11-21"},{"cvss_score":6.1,"headline":"WPQA \u003c 5.4 - Reflected Cross-Site Scripting","id":"CVE-2022-1597","kev_date_added":null,"published":"2022-06-06"},{"cvss_score":5.9,"headline":"WPQA \u003c 6.1.1 - Contributor+ Stored XSS","id":"CVE-2024-2375","kev_date_added":null,"published":"2024-07-03"},{"cvss_score":5.3,"headline":"WPQA \u003c 5.5 - Unauthenticated Private Message Disclosure","id":"CVE-2022-1598","kev_date_added":null,"published":"2022-06-06"},{"cvss_score":4.3,"headline":"WPQA \u003c 5.7 - Subscriber+ Private Message Disclosure via IDOR","id":"CVE-2022-2198","kev_date_added":null,"published":"2022-08-22"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Unknown"]},"summary":"Authenticated users can inject malicious scripts via profile fields in WPQA Builder, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2022-1051/"}