[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fcAU6_bRfedhcENB89p4-fiwx4NuvRe9QJMnckwjFGfM":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":39,"analysis":135,"fingerprints":248},"whereabouts-swarm","Whereabouts: Swarm","0.5.0","Florian Ziegler","https:\u002F\u002Fprofiles.wordpress.org\u002Fflorianziegler\u002F","\u003Cp>Use a widget or the shortcode [whereabouts-swarm] to display your current location anywhere on your website.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Please note:\u003C\u002Fstrong> The location will only be displayed if a location has been set.\u003C\u002Fp>\n\u003Ch4>Styling\u003C\u002Fh4>\n\u003Cp>There is \u003Cstrong>no extra styling\u003C\u002Fstrong>. You can however do it yourself, in your theme. This is what the HTML looks like, depending on what you decide to display (in the settings):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cdiv class=\"whereabouts-swarm-location\">\n    \u003Cimg class=\"whereabouts-swarm-icon\" src=\"...\" alt=\"\" \u002F>\n    \u003Cspan class=\"whereabouts-swarm-venue\">Venue Name\u003C\u002Fspan>\n    \u003Cspan class=\"whereabouts-swarm-city\">City Name\u003C\u002Fspan>\n    \u003Cspan class=\"whereabouts-swarm-country\">Country Name\u003C\u002Fspan>\n    \u003Cspan class=\"whereabouts-swarm-timezone\">UTC Time Zone\u003C\u002Fspan>\n\u003C\u002Fdiv>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>PHP 5.3\u003C\u002Fli>\n\u003Cli>WordPress 4.3\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Support\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fwhereabouts-swarm\" rel=\"ugc\">Open a new topic here\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Website\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwhereabouts.haptiq.dev\" rel=\"nofollow ugc\">Whereabouts\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Author\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fflorianziegler.de\" rel=\"nofollow ugc\">Website\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fdamndirty\" rel=\"nofollow ugc\">Twitter\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Display your current location, automatically updated by your latest Swarm check-in.",20,2903,100,1,"2020-09-28T06:54:00.000Z","5.5.18","4.3","",[20,21,22,23,24],"foursquare","location","swarm","timezone","travel","https:\u002F\u002Fwhereabouts.haptiq.dev\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwhereabouts-swarm.0.5.0.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":35,"avg_security_score":27,"avg_patch_time_days":36,"trust_score":37,"computed_at":38},"florianziegler",2,40,30,84,"2026-04-04T23:29:50.902Z",[40,56,78,99,118],{"slug":41,"name":42,"version":43,"author":7,"author_profile":8,"description":44,"short_description":45,"active_installs":11,"downloaded":46,"rating":13,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":18,"tags":51,"homepage":54,"download_link":55,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"whereabouts","Whereabouts","0.7.1","\u003Cp>Each user can save his\u002Fher current location and the corresponding time (zone). The information is stored as user meta data.\u003C\u002Fp>\n\u003Cp>The Whereabouts widget displays the location and time (zone) of a specified user (select user in the widget options).\u003C\u002Fp>\n\u003Cp>You can – of course – add multiple widgets to show more than one user\u002Flocation.\u003C\u002Fp>\n\u003Ch4>Dashboard-Widget\u003C\u002Fh4>\n\u003Cp>Each user can comfortably set her\u002Fhis current location directly on the WordPress dashboard.\u003C\u002Fp>\n\u003Ch4>A little help from Google\u003C\u002Fh4>\n\u003Cp>Activate the use of the Google Geocoding and Timezone API in the settings:\u003C\u002Fp>\n\u003Cp>You can then use the browser’s geolocation API to determine your location, and the Plugin will automatically fetch the time zone of your whereabouts.\u003C\u002Fp>\n\u003Cp>Want to use another location? Just type in a location name and the plugin will get all the relevant information for you.\u003C\u002Fp>\n\u003Cp>You can also set the language in which the results of the api requests are returned.\u003C\u002Fp>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>PHP 5.3\u003C\u002Fli>\n\u003Cli>WordPress 3.9.2\u003C\u002Fli>\n\u003Cli>In some modern browsers your website needs to have a working SSL-certificate in order to use the geolocation api.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Support\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fwhereabouts\" rel=\"ugc\">Open a new topic here\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Website\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwhere.abouts.io\u002F\" rel=\"nofollow ugc\">Whereabouts\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fflorianziegler\u002Fwhereabouts\" rel=\"nofollow ugc\">Github\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Author\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fflorianziegler.de\u002F\" rel=\"nofollow ugc\">Website\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fdamndirty\" rel=\"nofollow ugc\">Twitter\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Users can set their current location via the WordPress dashboard. A widget displays the location and the corresponding time (zone).",6421,5,"2023-07-25T15:41:00.000Z","4.6.30","3.9",[52,21,53,23,24],"digitalnomad","nomad","https:\u002F\u002Fwhere.abouts.io\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwhereabouts.0.7.1.zip",{"slug":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":64,"downloaded":65,"rating":66,"num_ratings":67,"last_updated":68,"tested_up_to":69,"requires_at_least":70,"requires_php":71,"tags":72,"homepage":76,"download_link":77,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"geolocation","Geolocation","1.9.7","Chris","https:\u002F\u002Fprofiles.wordpress.org\u002Ffrsh\u002F","\u003Cp>The Geolocation plugin allows WordPress users to geotag their posts using the Edit Post page.\u003C\u002Fp>\n\u003Cp>Previously, in all WordPress mobile applications such as WordPress for iPhone\u002FiPad, WordPress for Android this was directly available by activating the gps functionality. Unfortunately, the WP-application developers decided to deactivate the feature of storing GPS data in the app but I am hoping for its return.\u003C\u002Fp>\n\u003Cp>The automated way to obtain geoinformation is possible by adding a photo as featured image to your post. If you have a featured image attached to you post, its gps coordinates are taken into concideration if there is no geo-information provided already. If you use an iPhone, make sure that you take your photos in jpg. Otherwise the GPS information is stripped from the HEIC when exporting to JPG and uploading. Furthermore, when using the WP app, make sure you have enabled to keep all metadata in the files that are uploade. Otherwise, the app will remove also the GPS information.\u003C\u002Fp>\n\u003Cp>Once there is geoinformation added to any of your posts, visitors see a short description of the address either before, after, or at a custom location within the post. Here, you have three options as shown below: plain, link or static information.\u003Cbr \u002F>\nWhen “link” is chosen, hovering over the address reveals a map that displays the post’s exact location.\u003Cbr \u002F>\nIf one would only like to show a textual version without accessing any external services or without showing a map when visitors see a post, one can enable a “plain” mode to prevent external access except for authors to set a particular location.\u003Cbr \u002F>\nFurthermore, there is an option to statically show the map whenever there is geoinformation available. (see below for examples)\u003C\u002Fp>\n\u003Cp>You can chose between two map providers: Google Maps and Open Streetmaps.  If you use Open Streetmaps as mapprovider in combination with the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fosm-tiles-proxy\u002F\" title=\"proxy plugin for OSM\" rel=\"ugc\">proxy plugin for OSM\u003C\u002Fa>, the tiles are delivered from the local proxy so that the visitors cannot be tracked from a third party. If no proxy is installed or Google Maps is used as the provider, this is not feasable, i.e., the tiles are pulled directly from the map service to your visitor’s browser.\u003C\u002Fp>\n\u003Cp>Furthermore, there is the option to use the tag [geolocation] also on a page in order to provide a map with multiple entries (e.g. from a journey) on one map altogether. The set of shown locations can be filtered per page, by placing a user defined field called “category” and give it the name (not the slag!) of the category to be shown. This way, you can also hide the location information per post (by chosing the “code option” without using it) and only show an overview map if needed. If the page is not restricted by any of the categories, all locations are shown that were tagged “public” and have the switch set to “enabled”. (see example below)\u003C\u002Fp>\n\u003Cp>By default, this plugin uses Open-Streetmap but as an alternative (and backwards-compatibility) google maps can also be used. However, one needs to have a Goole Maps API key to use this plugin with google maps. You may obtain a key via google cloud plattform. Make sure, you have activated “Maps JavaScript API” as well as “Geocoding API”.\u003C\u002Fp>\n\u003Cp>If you struggle while installing it or have feature requests, please feel free to drop a \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fgeolocation\u002F\" title=\"support request\" rel=\"ugc\">support request\u003C\u002Fa> anytime. I am more than happy to help you. Also if you would want to give a \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fgeolocation\u002Freviews\u002F\" title=\"review\" rel=\"ugc\">review\u003C\u002Fa> if you are happy with the plugin, I would appreciate the feedback.\u003C\u002Fp>\n","Lightweight display the location information of your post in a map (GDPR comliant). Ideal for travelbloggers or anyone who would like to show the loca …",500,41633,78,11,"2025-05-24T19:44:00.000Z","6.8.5","6.0","7.3",[73,74,21,75,24],"gps","journey","map","https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fgeolocation\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fgeolocation.1.9.7.zip",{"slug":79,"name":80,"version":81,"author":82,"author_profile":83,"description":84,"short_description":85,"active_installs":86,"downloaded":87,"rating":88,"num_ratings":89,"last_updated":90,"tested_up_to":69,"requires_at_least":91,"requires_php":92,"tags":93,"homepage":97,"download_link":98,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"simple-location","Simple Location","5.0.24","David Shanske","https:\u002F\u002Fprofiles.wordpress.org\u002Fdshanske\u002F","\u003Cp>Supports adding geo coordinates, a location taxonomy, and a textual location description to a post, comment, user, or attachment. Supports adding weather data to a post or to a widget based on location.\u003Cbr \u002F>\nOffers choice of map displays. It supports retrieving location using the HTML5 geolocation API by default. Clicking the location icon or ‘Lookup Location’ will retrieve the location.\u003C\u002Fp>\n\u003Cp>As it stores the GeoData in the classic WordPress format, Geodata can also be added from other plugins.\u003C\u002Fp>\n\u003Cp>Automatically saves location data from image metadata when uploaded as well.\u003C\u002Fp>\n\u003Cp>Offers the opportunity to change the displayed timezone on a per-post basis for those posts from far off locations and set this based on the coordinates of the location.\u003Cbr \u002F>\nWhile Gutenberg compatible, this is not built for Gutenberg.\u003C\u002Fp>\n\u003Ch3>Privacy and Data Notice\u003C\u002Fh3>\n\u003Cp>Simple Location stores location and weather data inside posts, attachments, comments, and term meta…optionally other post types. This data respects a public, private or\u003Cbr \u002F>\nprotected setting. Attachment data is automatically extracted from images if location is present, which could be extracted by any third-party downloading the picture\u003Cbr \u002F>\nunless removed. For all other data, it is provided by the user, who decides its ultimate use. Location data is made available through a geolocation provider…the default is currently\u003Cbr \u002F>\nHTML5 browser geolocation, for which the user must give consent to share). Other information is secured through use of third-party APIs to identify a\u003Cbr \u002F>\nlocation, calculate elevation, display maps, and weather conditions.\u003C\u002Fp>\n\u003Ch3>Locations and Venues\u003C\u002Fh3>\n\u003Cp>Locations uses WordPress taxonomies to allow you to generate an archive page of all posts from that location and giving it a permalink on your site. Locations are meant to reflect a more general\u003Cbr \u002F>\nlocation…for example, “Here are posts I made in California.”\u003C\u002Fp>\n\u003Cp>Locations are divided by administrative areas. The hierarchy for locations is:\u003Cbr \u002F>\n* Country\u003Cbr \u002F>\n* Region – state, county, or province level.\u003Cbr \u002F>\n* Locality – city, town, or village level\u003C\u002Fp>\n\u003Cp>You can choose to display the location over the textual address field. There is an option in settings to change this behavior.\u003C\u002Fp>\n\u003Cp>The reverse geocoding system attempts to consistently retrieve the country code, region code, and locality for the location and add them to the location taxonomy. This can be potentially problematic, as if the returns\u003Cbr \u002F>\nfrom the locations added aren’t consistent, it will duplicate and explode the list of terms. This is the same issue that has held back venues.\u003C\u002Fp>\n\u003Cp>Locations are matched using the country code, region code, and locality field, and therefore, you can edit the displayed name or the region code without issue. Due to matching issues, you may have to make some manual changes and there may be some occasional duplication.\u003C\u002Fp>\n\u003Cp>There is no top level Location page, \u002Flocation included in the plugin. You can create a page at this location and use a custom template to allow it to show a list of your locations.\u003C\u002Fp>\n\u003Cp>Venues are meant to reflect a specific location, such as a business or point of interest. Venues were originally set up as a taxonomy, and were in the plugin unimplemented for several versions. However,\u003Cbr \u002F>\ndue to various changes since that was set up, they were switched to a custom post type. Under this setup, each venue is represented by a URL on the site that posts can be linked to. The URL contains\u003Cbr \u002F>\ninformation about the venue.\u003C\u002Fp>\n\u003Ch3>Zones\u003C\u002Fh3>\n\u003Cp>Zones allow for geofencing. You can set coordinates and a radius around them. If you set location to a place within a zone, the default behavior is to replace the location\u003Cbr \u002F>\nwith a preset Name and hide the coordinates. This allows you to protect private locations such as your home, or your place of business. For Micropub, it will set the location\u003Cbr \u002F>\nas protected if the location is in the zone and the location-visibility property is not set. For the post editor in WordPress, looking up the location of an item inside the\u003Cbr \u002F>\nzone will result in the visibility being set to protected and the name being set to the zone name. This can be overridden.\u003C\u002Fp>\n\u003Cp>Zones are replaced as of 5.0.0 with Private Venues\u003C\u002Fp>\n\u003Ch3>Weather\u003C\u002Fh3>\n\u003Cp>Weather consists of at minimum the current conditions and temperature but includes future parameters for use such as pressure, wind speed, wind direction degree, etc. Weather widgets are available\u003Cbr \u002F>\nthat can be set to a specific location, a user, station ID, or airport code. Station ID is available from supported providers for weather stations, for example from a Personal Weather Station(PWS).\u003C\u002Fp>\n\u003Ch3>Stations\u003C\u002Fh3>\n\u003Cp>Stations allow for using a custom data source for weather data. This source should be a URL that returns a JSON object. When using the Custom Station provider for weather, it\u003Cbr \u002F>\nwill look for when one of the stations defined is within 10km of your current location. It will then use the return as the current weather conditions. Please note that the\u003Cbr \u002F>\nreturn must be in the format documented in the code.\u003C\u002Fp>\n\u003Ch3>WordPress GeoData\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FGeodata\" rel=\"nofollow ugc\">WordPress Geodata\u003C\u002Fa> is an existing standardized way to store geodata about a post, user, comment, or term.\u003C\u002Fp>\n\u003Cp>It consists of four fields: latitude, longitude, public, and address. This matches up with the HTML5 Geolocation fields. The \u003Ca href=\"https:\u002F\u002Fdev.w3.org\u002Fgeo\u002Fapi\u002Fspec-source.html\" rel=\"nofollow ugc\">W3C Geolocation Specification\u003C\u002Fa>\u003Cbr \u002F>\nalso provides for properties of altitude, accuracy, altitudeAccuracy, speed, and heading, which may be stored. Map Zoom is also stored as a geodata property.\u003C\u002Fp>\n\u003Cp>Timezone is also stored as a property and is derived from the location by default or set manually.\u003C\u002Fp>\n\u003Cp>In order to access private location information, the following custom capabilities are added to WordPress:\u003Cbr \u002F>\n* ‘read_{$object_type}\u003Cem>location’ – Whether or not a user is allowed to read information locations for object types: posts, comments, terms, users. A user is always allowed to read the location from their objects.\u003Cbr \u002F>\n* ‘edit\u003C\u002Fem>{$object_type}_location’ – Whether or not a user is allowed to edit information locations for object types: posts, comments, terms, users. A user is always allowed to read the location from their objects.\u003C\u002Fp>\n\u003Ch3>Providers\u003C\u002Fh3>\n\u003Cp>The plugin is designed to be extensible and anyone could write a plugin that would add additional providers.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Map Providers are services that offer an API to retrieve maps, which are displayed on posts with a location. Providers include MapBox, Google, Mapquest, HERE, LocationIQ, Geoapify, TomTom, and Bing.\u003C\u002Fli>\n\u003Cli>Geocoding Providers take geo coordinates and look up the actual location\u002Faddress for textual display. Geocoding Providers include Nominatim, HERE, the Mapquest hosted version of Nominatim, Google, Bing, LocationIQ, OpenRoute and Geonames. They also support looking up coordinate for physical addresses\u003C\u002Fli>\n\u003Cli>Venue providers, similar to Geocoding providers, search for locations from coordinates, however, instead of returning street addresses, or municipality, it returns a list of places or venues.\u003C\u002Fli>\n\u003Cli>Elevation Providers optionally derive the elevation from an API when not available. Elevation is used to estimate altitude and adjust estimated sunrise\u002Fsunset levels accordingly.\u003C\u002Fli>\n\u003Cli>Location Providers attempt to determine your location to add it to a post. Providers include  HTML5 Browser Geolocation, a Provider that takes the location setting out of the author profile, a provider that returns the exact\u003Cbr \u002F>\nlocation of a three letter airport code, and \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Faaronpk\u002FCompass\" rel=\"nofollow ugc\">Compass\u003C\u002Fa>, a self-hosted option for storing your location.\u003C\u002Fli>\n\u003Cli>Weather Providers retrieve weather data about your location and include OpenWeatherMap, Pirate Weather, Dark Sky, Weatherstack, WeatherBit, HERE and the US National Weather Service. HERE, Pirate Weather, Dark Sky, WeatherBit, and Weatherstack do not support stations. There is also an option for custom station URLs that must return the properties as they are stored in WordPress.\u003Cbr \u002F>\n** The National Weather Service(US) uses their station lookup API to find the closest weather station, and uses weather from there. Therefore, if this returns no options, if you are outside the US, it will return no weather.\u003Cbr \u002F>\n** The Met Office(UK) uses the distance from your current location to the nearest UK weather station and finds the closest one. However, if the nearest station is more than 100km away, it will return nothing.\u003Cbr \u002F>\n** For Weather services like the NWS, Met Office, and the Custom Provider, where coverage is not worldwide, if nothing is found, a fallback provider can be set and used.\u003C\u002Fli>\n\u003C\u002Ful>\n","Adds geographic location and weather support to WordPress.",300,58726,92,8,"2026-02-25T21:08:00.000Z","6.2","7.4",[94,57,21,95,96],"geo","maps","timezones","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsimple-location\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsimple-location.5.0.24.zip",{"slug":100,"name":101,"version":102,"author":103,"author_profile":104,"description":105,"short_description":106,"active_installs":107,"downloaded":108,"rating":28,"num_ratings":28,"last_updated":18,"tested_up_to":109,"requires_at_least":110,"requires_php":18,"tags":111,"homepage":115,"download_link":116,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":117},"gi-weather","GI Weather","1.0.0","GICoder","https:\u002F\u002Fprofiles.wordpress.org\u002Fgicoder\u002F","\u003Cp>GI Weather Plugin is a simple tool that help you to obtain current weather data for any city in the world.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Retrieve weather data for a certain city or by tracing user loaction. \u003C\u002Fli>\n\u003Cli>Ready to use Widget. \u003C\u002Fli>\n\u003Cli>Shortcodes ready. \u003C\u002Fli>\n\u003Cli>BuddyPress Profile Integration.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For more information about the plugin or how to use shortcodes you can \u003Ca href=\"http:\u002F\u002Fgicoder.net\u002Fdocs\u002Fgi-weather\u002F\" rel=\"nofollow ugc\">visit GI Coder website\u003C\u002Fa>\u003C\u002Fp>\n","GI Weather Plugin is a simple tool that help you to obtain current weather data for any city in the world.",10,2128,"4.1.42","4.0",[112,21,113,23,114],"forcasting","open-weathr-api","weather","http:\u002F\u002Fgicoder.net\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fgi-weather.zip","2026-03-15T10:48:56.248Z",{"slug":119,"name":120,"version":121,"author":122,"author_profile":123,"description":124,"short_description":125,"active_installs":107,"downloaded":126,"rating":127,"num_ratings":14,"last_updated":18,"tested_up_to":128,"requires_at_least":129,"requires_php":18,"tags":130,"homepage":133,"download_link":134,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":117},"travel-routes","Travel Routes","1.1","WebMaestro.Fr","https:\u002F\u002Fprofiles.wordpress.org\u002Fwebmaestrofr\u002F","\u003Cp>Easily add geographical tags on a map when you write a post, and it will automatically create new countries and localities terms. You can also order those locations randomly or by date to define your routes.\u003C\u002Fp>\n\u003Cp>Use the map as a widget, and pick your own colors to customize it. It is a SVG map that react to users actions (mouse over posts and terms links, click on route line…).\u003C\u002Fp>\n\u003Cp>Ask your questions on \u003Ca href=\"http:\u002F\u002Fwebmaestro.fr\u002Fblog\u002Ftravel-routes-wordpress-plugin\u002F\" title=\"Plugin Page\" rel=\"nofollow ugc\">the plugin page\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fouestetienne.com\" title=\"Demo\" rel=\"nofollow ugc\">See the demo\u003C\u002Fa> !\u003C\u002Fp>\n\u003Cp>This plugin is open for \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FWebMaestroFr\u002FTravel-Routes-Wordpress-Plugin\" title=\"GitHub\" rel=\"nofollow ugc\">contributions\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Known issues\u003C\u002Fh3>\n\u003Cp>An OVER_QUERY_LIMIT error from the \u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Fmaps\u002Fdocumentation\u002Fgeocoding\u002F\" title=\"Google Geocoding API\" rel=\"nofollow ugc\">Google Geocoding API\u003C\u002Fa> is showing up way too often. If any contributor could \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FWebMaestroFr\u002FTravel-Routes-Wordpress-Plugin\u002Fblob\u002Fmaster\u002Fadmin.php#LC138\" title=\"Bug\" rel=\"nofollow ugc\">take a look at the insert_term() function\u003C\u002Fa>, that would be awesome.\u003C\u002Fp>\n","Display your travels on customizable maps !",2600,80,"3.4.2","3.4",[131,21,75,132,24],"customizable","route","http:\u002F\u002Fwebmaestro.fr\u002Fblog\u002Ftravel-routes-wordpress-plugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftravel-routes.zip",{"attackSurface":136,"codeSignals":179,"taintFlows":209,"riskAssessment":236,"analyzedAt":247},{"hooks":137,"ajaxHandlers":170,"restRoutes":171,"shortcodes":172,"cronEvents":177,"entryPointCount":14,"unprotectedCount":28},[138,144,148,153,158,162,166],{"type":139,"name":140,"callback":141,"file":142,"line":143},"action","wp","whereabouts_swarm_setup_schedule","includes\\get-location.php",15,{"type":139,"name":145,"callback":146,"file":142,"line":147},"whereabouts_swarm_fetch_location","whereabouts_swarm_fetch_location_go",63,{"type":139,"name":149,"callback":150,"file":151,"line":152},"widgets_init","whereabouts_swarm_register_widgets","includes\\widget.php",75,{"type":139,"name":154,"callback":155,"file":156,"line":157},"after_setup_theme","whereabouts_swarm_setup","whereabouts-swarm.php",47,{"type":139,"name":159,"callback":160,"file":156,"line":161},"init","whereabouts_swarm_init",73,{"type":139,"name":163,"callback":164,"file":156,"line":165},"admin_menu","whereabouts_swarm_menu",91,{"type":139,"name":167,"callback":168,"file":156,"line":169},"admin_init","whereabouts_swarm_register_settings",197,[],[],[173],{"tag":4,"callback":174,"file":175,"line":176},"whereabouts_swarm_display_location","includes\\display-location.php",98,[178],{"hook":145,"callback":145,"file":142,"line":67},{"dangerousFunctions":180,"sqlUsage":181,"outputEscaping":183,"fileOperations":28,"externalRequests":14,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":208},[],{"prepared":28,"raw":28,"locations":182},[],{"escaped":34,"rawEcho":184,"locations":185},12,[186,188,189,191,193,195,197,199,200,202,204,206],{"file":142,"line":35,"context":187},"raw output",{"file":151,"line":36,"context":187},{"file":151,"line":190,"context":187},32,{"file":151,"line":192,"context":187},34,{"file":151,"line":194,"context":187},35,{"file":151,"line":196,"context":187},61,{"file":151,"line":198,"context":187},62,{"file":151,"line":198,"context":187},{"file":156,"line":201,"context":187},117,{"file":156,"line":203,"context":187},129,{"file":156,"line":205,"context":187},140,{"file":156,"line":207,"context":187},145,[],[210,228],{"entryPoint":211,"graph":212,"unsanitizedCount":14,"severity":227},"whereabouts_swarm_load_menu_page (whereabouts-swarm.php:94)",{"nodes":213,"edges":224},[214,219],{"id":215,"type":216,"label":217,"file":156,"line":218},"n0","source","$_GET['swarm_auth_code']",152,{"id":220,"type":221,"label":222,"file":156,"line":218,"wp_function":223},"n1","sink","update_option() [Settings Manipulation]","update_option",[225],{"from":215,"to":220,"sanitized":226},false,"low",{"entryPoint":229,"graph":230,"unsanitizedCount":14,"severity":227},"\u003Cwhereabouts-swarm> (whereabouts-swarm.php:0)",{"nodes":231,"edges":234},[232,233],{"id":215,"type":216,"label":217,"file":156,"line":218},{"id":220,"type":221,"label":222,"file":156,"line":218,"wp_function":223},[235],{"from":215,"to":220,"sanitized":226},{"summary":237,"deductions":238},"The whereabouts-swarm plugin v0.5.0 presents a mixed security posture. On the positive side, there are no known CVEs, no bundled libraries, and all SQL queries are properly prepared, indicating good foundational security practices. The attack surface is also minimal, with no unprotected entry points identified through AJAX or REST API handlers. However, several areas raise concerns. The plugin exhibits a very low percentage of properly escaped output, meaning a significant portion of user-facing data could be vulnerable to Cross-Site Scripting (XSS) attacks. Furthermore, the taint analysis reveals two flows with unsanitized paths, which, while not categorized as critical or high severity in this analysis, represent a potential vector for data manipulation or execution if exploited. The absence of nonce checks and capability checks on its identified entry points (shortcodes and cron events) is a notable weakness, leaving these functions potentially open to unauthorized actions.",[239,241,243,245],{"reason":240,"points":89},"Low output escaping percentage",{"reason":242,"points":47},"Taint analysis shows unsanitized paths",{"reason":244,"points":107},"No nonce checks",{"reason":246,"points":107},"No capability checks","2026-03-16T22:58:09.141Z",{"wat":249,"direct":258},{"assetPaths":250,"generatorPatterns":253,"scriptPaths":254,"versionParams":255},[251,252],"\u002Fwp-content\u002Fplugins\u002Fwhereabouts-swarm\u002Fcss\u002Fwhereabouts-swarm-admin.css","\u002Fwp-content\u002Fplugins\u002Fwhereabouts-swarm\u002Fjs\u002Fwhereabouts-swarm.min.js",[],[],[256,257],"whereabouts-swarm\u002Fcss\u002Fwhereabouts-swarm-admin.css?ver=","js\u002Fwhereabouts-swarm.min.js?ver=",{"cssClasses":259,"htmlComments":261,"htmlAttributes":273,"restEndpoints":278,"jsGlobals":279,"shortcodeOutput":281},[260],"whereabouts-swarm-form",[262,263,264,265,266,267,268,269,270,271,272],"\u003C!-- Plugin Setup -->","\u003C!-- Define include path for this plugin -->","\u003C!-- Define url for this plugin -->","\u003C!-- Define version -->","\u003C!-- Load language files -->","\u003C!-- Enqueue styles and scripts -->","\u003C!-- Register settings menu for Whereabouts Swarm -->","\u003C!-- De-Authentication -->","\u003C!-- Authentification -->","\u003C!-- Fetch Location -->","\u003C!-- Display Settings -->",[274,275,276,277],"data-whereabouts-swarm-venue-icon","data-whereabouts-swarm-venue-link","data-whereabouts-swarm-venue-website-link","data-whereabouts-swarm-venue-website-link-text",[],[280],"window.whereabouts_swarm",[]]