All In One RedirectionWordPress extension · Vsourz
CVE-2024-37245
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Vsourz Digital All In One Redirection allows Reflected XSS.This issue affects All In One Redirection: from n/a through 2.2.0.
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 confidenceA reflected XSS vulnerability exists in the Vsourz Digital All In One Redirection WordPress plugin (versions up to 2.2.0). The plugin fails to properly sanitize user-supplied input before reflecting it back in web pages, allowing attackers to inject malicious JavaScript that executes in victim's browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
All In One RedirectionWordPress extension
<= 2.2.0CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Locate the Vsourz plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'all-in-one-redirection' or similar Vsourz Digital plugin folderAffected if The plugin folder exists in the WordPress plugins directory
-
Identify the installed versionOpen the main plugin PHP file (usually the primary .php file in the plugin folder) and look for the 'Version' header comment in the file, or check the plugin's readme.txt fileAffected if The version listed is 2.2.0 or lower
-
Verify plugin statusIn WordPress admin, go to Plugins > Installed Plugins and check whether the Vsourz All In One Redirection plugin is activatedAffected if The plugin shows as 'Active' in the WordPress admin plugins list
-
Confirm vulnerability scopeCompare your installed version against the affected range: versions 2.2.0 and belowAffected if The installed version is 2.2.0 or any version up to 2.2.0
Your environment is affected if the Vsourz Digital All In One Redirection plugin is installed, active, and running version 2.2.0 or lower.
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 to a patched version when available. Until then, implement web application firewall rules to block XSS attack patterns and apply HTML encoding/URL encoding to all user input before reflecting it in responses.
latest available version (2.2.1 or higher)
- 1. Update the All In One Redirection plugin to the latest available version from the WordPress plugin repository
- 2. After updating, verify the plugin is functioning correctly by testing redirection rules
- 3. Clear any server-side caches if applicable
- 4. Confirm the update was successful by checking the plugin version number in WordPress admin under Plugins
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in All In One Redirection
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37245 — 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-2024-37245 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