{"uuid": "c178b0e6-7c3a-4b4a-b4b8-eb985546a8b1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2013-0235", "type": "seen", "source": "https://github.com/rapid7/metasploit-framework/blob/master/modules/auxiliary/scanner/http/wordpress_pingback_access.rb", "content": "{\"actions\": [], \"aliases\": [], \"arch\": \"\", \"author\": [\"Thomas McCarthy \\\"smilingraccoon\\\" \", \"Brandon McCann \\\"zeknox\\\" \", \"Christian Mehlmauer \"], \"autofilter_ports\": [80, 8080, 443, 8000, 8888, 8880, 8008, 3000, 8443], \"autofilter_services\": [\"http\", \"https\"], \"check\": false, \"default_credential\": false, \"description\": \"This module will scan for wordpress sites with the Pingback\\n          API enabled. By interfacing with the API an attacker can cause\\n          the wordpress site to port scan an external target and return\\n          results. Refer to the wordpress_pingback_portscanner module.\\n          This issue was fixed in wordpress 3.5.1\", \"disclosure_date\": null, \"fullname\": \"auxiliary/scanner/http/wordpress_pingback_access\", \"is_install_path\": true, \"mod_time\": \"2025-06-23 12:43:46 +0000\", \"name\": \"Wordpress Pingback Locator\", \"needs_cleanup\": false, \"notes\": {\"Reliability\": [\"unknown-reliability\"], \"SideEffects\": [\"unknown-side-effects\"], \"Stability\": [\"unknown-stability\"]}, \"path\": \"/modules/auxiliary/scanner/http/wordpress_pingback_access.rb\", \"platform\": \"\", \"post_auth\": false, \"rank\": 300, \"ref_name\": \"scanner/http/wordpress_pingback_access\", \"references\": [\"CVE-2013-0235\", \"URL-https://bugtraq.securityfocus.com/archive/1/525045/30/30/threaded\", \"URL-http://www.ethicalhack3r.co.uk/security/introduction-to-the-wordpress-xml-rpc-api/\", \"URL-https://github.com/FireFart/WordpressPingbackPortScanner\"], \"rport\": 80, \"session_types\": false, \"targets\": null, \"type\": \"auxiliary\"}", "creation_timestamp": "2026-09-08T06:47:55.913707Z"}