{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-4119 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4119 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4119 is a critical missing authorization vulnerability in jppreus Create DB Tables, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-4119 and fix it if it is affected.\n\nWhat it is: CVE-2026-4119 is a critical missing authorization vulnerability in jppreus Create DB Tables, published on 22 Apr 2026. 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-2026-4119 in the wild and no public exploit code.\n\nAffected product: jppreus Create DB Tables. 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-2026-4119/ (Markdown: https://insights.sbomify.com/CVE-2026-4119/index.md)","id":"CVE-2026-4119","markdown":"https://insights.sbomify.com/CVE-2026-4119/index.md","name":"CVE-2026-4119","record":{"aliases":["GHSA-jpj9-vrh6-4wmc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Authenticated subscribers can arbitrarily create or delete database tables, potentially destroying the WordPress installation, due to missing capability checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Create DB Tables plugin for WordPress is vulnerable to authorization bypass in all versions up to and including 1.2.1. The plugin registers admin_post action hooks for creating tables (admin_post_add_table) and deleting tables (admin_post_delete_db_table) without implementing any capability checks via current_user_can() or nonce verification via wp_verify_nonce()/check_admin_referer(). The admin_post hook only requires the user to be logged in, meaning any authenticated user including Subscribers can access these endpoints. The cdbt_delete_db_table() function takes a user-supplied table name from $_POST['db_table'] and executes a DROP TABLE SQL query, allowing any authenticated attacker to delete any database table including critical WordPress core tables such as wp_users or wp_options. The cdbt_create_new_table() function similarly allows creating arbitrary tables. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create arbitrary database tables and delete any existing database table, potentially destroying the entire WordPress installation.","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 Create DB Tables","id":"CVE-2026-4119","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":13,"next":{"headline":"Info Cards \u003c= 2.0.7 - Authenticated (Contributor+) Stored Cross-Site Scripting via Block Attributes","id":"CVE-2026-4120"},"packages":[],"prev":{"headline":"Call To Action Plugin \u003c= 3.1.3 - Cross-Site Request Forgery via Settings Update","id":"CVE-2026-4118"},"products":["Create DB Tables"],"published":"2026-04-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-22","vendors":["jppreus"]},"summary":"Authenticated subscribers can arbitrarily create or delete database tables, potentially destroying the WordPress installation, due to missing capability checks.","url":"https://insights.sbomify.com/CVE-2026-4119/"}