SirvWordPress extension
CVE-2025-46233
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 ('Cross-site Scripting') vulnerability in Sirv CDN and Image Hosting Sirv sirv allows Stored XSS.This issue affects Sirv: from n/a through <= 7.5.3.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in Sirv CDN and Image Hosting allows malicious scripts to be injected and persisted on the server, executing when other users view the affected content. The vulnerability stems from improper neutralization of input during web page generation.
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
SirvWordPress extension
< 7.5.4CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Sirv installationIdentify if Sirv CDN or Image Hosting is deployed in your environment. Check for sirv-related processes, services, or web applications.Affected if Sirv is installed and running
-
Check installed versionLocate the installed Sirv version by accessing the application admin panel, checking the software bill of materials, or querying the service endpoint for version information.Affected if Installed version is lower than 7.5.4
-
Identify user content entry pointsReview which features accept user-supplied input such as file descriptions, comments, metadata fields, or profile information. Check if the image upload/management interface allows text input.Affected if User-controllable text fields exist in the application
-
Verify output encoding is appliedInspect how user-supplied content is rendered in the application. Examine the HTML source of pages displaying uploaded file metadata, descriptions, or any user-generated text.Affected if User input appears unescaped in rendered HTML (e.g., <script> tags work, event handlers like onload= execute)
You are affected if Sirv CDN/Image Hosting is running and the installed version is below 7.5.4, with user-generated content features accessible to inject and persist malicious scripts.
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 · scoped7.5.4
Implement proper input validation and sanitization on all user-supplied content, combined with context-aware output encoding when rendering content in web pages to neutralize malicious script payloads.
7.5.4
- Upgrade Sirv to version 7.5.4 or later to remediate the stored XSS vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Sirv
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46233 — 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-46233 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