{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-9881 exists.","fix":"No fix has been published for CVE-2019-9881 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-9881 is a medium-severity missing authorization vulnerability in n/a, published on 10 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-9881 and fix it if it is affected.\n\nWhat it is: CVE-2019-9881 is a medium-severity missing authorization vulnerability in n/a, published on 10 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-9881 exists.\n\nAffected product: n/a. 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-2019-9881/ (Markdown: https://insights.sbomify.com/CVE-2019-9881/index.md)","id":"CVE-2019-9881","markdown":"https://insights.sbomify.com/CVE-2019-9881/index.md","name":"CVE-2019-9881","record":{"aliases":["GHSA-hhwc-x32h-p6qg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can post comments on any article in WPGraphQL, bypassing comment restrictions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wpgraphql","vendor":"wpengine"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"The createComment mutation in the WPGraphQL 0.2.3 plugin for WordPress allows unauthenticated users to post comments on any article, even when 'allow comment' is disabled.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-05-21","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":"2019-05-21","kind":"exploitdb","ref":"46886","stars":null,"title":"WordPress Plugin WPGraphQL 0.2.3 - Multiple Vulnerabilities"},{"date":null,"kind":"nuclei","ref":"http/cves/2019/CVE-2019-9881.yaml","stars":null,"title":"WPEngine WPGraphQL 0.2.3 - Unauthenticated Comment Posting"}],"tier":"weaponised"},"has_fix":false,"headline":"Missing authorization in n/a","id":"CVE-2019-9881","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2019"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site request forgery in MailSherlock MSR35","id":"CVE-2019-9882"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-9880"},"products":["n/a"],"published":"2019-06-10","related":[{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2019-9879","kev_date_added":null,"published":"2019-06-10"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2019-9880","kev_date_added":null,"published":"2019-06-10"},{"cvss_score":5.3,"headline":"WPGraphQL WooCommerce \u003c= 0.11.0 - Unauthenticated Coupon Codes Disclosure","id":"CVE-2022-1563","kev_date_added":null,"published":"2024-01-16"},{"cvss_score":4.4,"headline":"WordPress WPGraphQL Plugin \u003c= 1.14.5 is vulnerable to Server Side Request Forgery (SSRF)","id":"CVE-2023-23684","kev_date_added":null,"published":"2023-11-13"}],"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":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Unauthenticated attackers can post comments on any article in WPGraphQL, bypassing comment restrictions.","url":"https://insights.sbomify.com/CVE-2019-9881/"}