{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-5411 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5411 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5411 is a high-severity vulnerability in webfactory Advanced Google reCAPTCHA, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5411 and fix it if it is affected.\n\nWhat it is: CVE-2026-5411 is a high-severity vulnerability in webfactory Advanced Google reCAPTCHA, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-5411 in the wild and no public exploit code.\n\nAffected product: webfactory Advanced Google reCAPTCHA. 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-5411/ (Markdown: https://insights.sbomify.com/CVE-2026-5411/index.md)","id":"CVE-2026-5411","markdown":"https://insights.sbomify.com/CVE-2026-5411/index.md","name":"CVE-2026-5411","record":{"aliases":["GHSA-pvjf-9qxm-hpmx"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can upload arbitrary files including webshells via license meta injection, leading to remote code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"The WP Captcha PRO (the premium version of the Advanced Google reCAPTCHA plugin, both have the same slug) plugin for WordPress is vulnerable to arbitrary file upload in all versions up to, and including, 5.38. This is due to a capability check in the save_ajax() function of the licensing module, combined with unrestricted file extraction in sync_cloud_protection(). This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files including PHP webshells to the server by injecting a malicious cloud_protection_url into the license meta, which the plugin then downloads and extracts without file type validation into a web-accessible uploads directory. This can be used for remote code execution. Note: The vulnerability can only be exploited with a remote URL if \"allow_url_fopen\" is enabled in the php.ini config.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-06-17","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-06-17T09:47:24Z","kind":"github_poc","ref":"https://github.com/izxci/CVE-2026-5411","stars":0,"title":"CVE-2026-5411 WP Captcha PRO"}],"tier":"poc_unverified"},"has_fix":null,"headline":"WP Captcha PRO \u003c= 5.38 - Missing Authorization to Authenticated (Subscriber+) Arbitrary File Upload","id":"CVE-2026-5411","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Juju CloudSpec API could leak senstive information","id":"CVE-2026-5412"},"packages":[],"prev":{"headline":"Redux Framework \u003c= 4.5.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Spinner Field Input","id":"CVE-2026-5410"},"products":["Advanced Google reCAPTCHA"],"published":"2026-06-05","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-06","vendors":["webfactory"]},"summary":"Authenticated attackers can upload arbitrary files including webshells via license meta injection, leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2026-5411/"}