CVE-2025-49329
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Agile Logix Store Locator WordPress agile-store-locator allows Upload a Web Shell to a Web Server.This issue affects Store Locator WordPress: from n/a through <= 1.5.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceUnrestricted file upload vulnerability in Agile Store Locator WordPress plugin versions <= 1.5.2 allows unauthenticated attackers to upload arbitrary files including web shells to the web server, potentially enabling remote code execution and complete site compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Agile Store Locator plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Agile Store Locator' in the list, or check the /wp-content/plugins/ directory for the agile-store-locator folderAffected if The plugin folder agile-store-locator exists in the plugins directory
-
Determine installed plugin versionIn WordPress admin Plugins page, click 'View Details' next to Agile Store Locator to see the version number, or open the main plugin PHP file (e.g., agile-store-locator.php) and check the Version header in the plugin comment blockAffected if Version displayed is 1.5.2 or lower
-
Confirm version is in vulnerable rangeCompare the installed version against the affected range: any version <= 1.5.2 is vulnerableAffected if Installed version is 1.5.2 or any earlier version (e.g., 1.5.1, 1.5.0, 1.0.0)
-
Check if upload functionality is accessibleExamine the plugin settings in WordPress admin under Store Locator > Settings to see if any file upload or import features are enabled or exposed; also check if the plugin exposes any frontend upload endpointsAffected if Upload, import, or file management features are available and accessible to unauthenticated users
If Agile Store Locator plugin is installed with version 1.5.2 or lower and the upload/import feature is enabled or exposed, the environment is affected by this unrestricted file upload vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Agile Store Locator plugin to the latest patched version that implements proper file type validation, extension checking, and content-type verification for uploaded files.
Latest version after 1.5.2 (plugin vendor should be contacted for exact fixed release)
- Update the Agile Store Locator WordPress plugin to the latest available version from the official WordPress plugin repository or the vendor
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49329 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data