{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-11007 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-11007 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-11007 is a medium-severity missing authorization vulnerability in n/a, published on 20 Sep 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-2016-11007 and fix it if it is affected.\n\nWhat it is: CVE-2016-11007 is a medium-severity missing authorization vulnerability in n/a, published on 20 Sep 2019. 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-2016-11007 in the wild and no public exploit code.\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-2016-11007/ (Markdown: https://insights.sbomify.com/CVE-2016-11007/index.md)","id":"CVE-2016-11007","markdown":"https://insights.sbomify.com/CVE-2016-11007/index.md","name":"CVE-2016-11007","record":{"aliases":["GHSA-884r-668x-5w95"],"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":"An attacker can retrieve invoices belonging to other users due to incorrect access control in the wp-invoice plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wp-invoice","vendor":"usabilitydynamics"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","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-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"The wp-invoice plugin before 4.1.1 for WordPress has incorrect access control over wpi_user_id for invoice retrieval.","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":"Missing authorization in n/a","id":"CVE-2016-11007","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"The wp-invoice plugin before 4.1.1 for WordPress has incorrect access control over wpi_paypal payer metadata updates.","id":"CVE-2016-11008"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2016-11006"},"products":["n/a"],"published":"2019-09-20","related":[{"cvss_score":6.5,"headline":"Privilege escalation in n/a","id":"CVE-2016-11011","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":6.1,"headline":"WP-Invoice \u003c= 4.3.1 - Stored Cross-Site Scripting via CSRF","id":"CVE-2022-1617","kev_date_added":null,"published":"2024-01-16"},{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2016-11006","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":5.3,"headline":"The wp-invoice plugin before 4.1.1 for WordPress has incorrect access control over wpi_paypal payer metadata updates.","id":"CVE-2016-11008","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":5.3,"headline":"The wp-invoice plugin before 4.1.1 for WordPress has incorrect access control over wpi_interkassa payer metadata updates.","id":"CVE-2016-11009","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":5.3,"headline":"The wp-invoice plugin before 4.1.1 for WordPress has incorrect access control over wpi_twocheckout payer metadata updates.","id":"CVE-2016-11010","kev_date_added":null,"published":"2019-09-20"}],"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-06","vendors":["n/a"]},"summary":"An attacker can retrieve invoices belonging to other users due to incorrect access control in the wp-invoice plugin.","url":"https://insights.sbomify.com/CVE-2016-11007/"}