ayecode vulnerabilities
Recent CVEs affecting ayecode products. 6 tracked.
ayecode has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 6. Most recent: 2025-07-11. Highest priority: CVE-2025-6200 (score 30/100).
- CVE-2025-6200 MEDIUM 5.9 UPGRADE The GeoDirectory WordPress plugin before 2.8.120 does not validate and escape some of its shortcode attribute
- CVE-2024-56259 MEDIUM 6.5 UPGRADE Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Paolo Ge
- CVE-2024-50437 MEDIUM 6.5 UPGRADE Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Paolo Ge
- CVE-2024-43981 MEDIUM 4.3 UPGRADE Missing Authorization vulnerability in AyeCode – WP Business Directory Plugins GeoDirectory allows Exploiting
- CVE-2024-43973 MEDIUM 4.3 UPGRADE Missing Authorization vulnerability in Stiofan GetPaid invoicing allows Exploiting Incorrectly Configured Acce
- CVE-2024-13590 MEDIUM 6.4 UPGRADE The Ketchup Shortcodes plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'spa
FAQ
How do I fix ayecode vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is ayecode being exploited right now?
None of the tracked ayecode CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which ayecode CVE should I patch first?
CVE-2025-6200 currently ranks highest (30/100): The GeoDirectory WordPress plugin before 2.8.120 does not validate and escape some of its shortcode attribute.