{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92553 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-92553 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92553 is a high-severity vulnerability in yaycommerce YaySMTP – WP Mail SMTP with Email Logs, Tracking \u0026 Reports, published on 16 Oct 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-92553 and fix it if it is affected.\n\nWhat it is: CVE-2026-92553 is a high-severity vulnerability in yaycommerce YaySMTP – WP Mail SMTP with Email Logs, Tracking \u0026 Reports, published on 16 Oct 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-92553 in the wild and no public exploit code.\n\nAffected product: yaycommerce YaySMTP – WP Mail SMTP with Email Logs, Tracking \u0026 Reports. 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-92553/ (Markdown: https://insights.sbomify.com/CVE-2026-92553/index.md)","id":"CVE-2026-92553","markdown":"https://insights.sbomify.com/CVE-2026-92553/index.md","name":"CVE-2026-92553","record":{"aliases":["GHSA-2875-475c-qvhr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can upload executable files via attachment filenames, leading to remote code execution on servers ignoring .htaccess guards.","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 YaySMTP – WP Mail SMTP with Email Logs, Tracking \u0026 Reports plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 2.7.7 via the putFile function. This is due to insufficient file type validation in the putFile function, as sanitize_file_name() does not strip executable extensions and no allow-list, MIME check, or safe-extension rename is applied. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload files that may be executable, which makes remote code execution possible. The only server-side guard is a .htaccess file containing 'Require all denied' written by writeGuards(), which is silently ignored by nginx and by Apache configured with AllowOverride None, meaning RCE is fully achievable on those server configurations.","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":"YaySMTP \u003c= 2.7.7 - Authenticated (Subscriber+) Arbitrary File Upload via Attachment Filename Extension","id":"CVE-2026-92553","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ShopLentor \u003c= 3.5.1 - Reflected Cross-Site Scripting via Query-String Parameter Name","id":"CVE-2026-92554"},"packages":[],"prev":{"headline":"Cross-site scripting in Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile \u0026 Restrict Content – ProfilePress","id":"CVE-2026-92551"},"products":["YaySMTP – WP Mail SMTP with Email Logs, Tracking \u0026 Reports"],"published":"2026-10-16","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["yaycommerce"]},"summary":"Authenticated subscribers can upload executable files via attachment filenames, leading to remote code execution on servers ignoring .htaccess guards.","url":"https://insights.sbomify.com/CVE-2026-92553/"}