CVE-2025-58267
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Aftabul Islam Stock Message stock-message allows Stored XSS.This issue affects Stock Message: from n/a through <= 1.1.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 CSRF vulnerability in the Stock Message plugin allows attackers to craft malicious requests that inject XSS payloads into stored messages. When authenticated users unknowingly trigger these requests (e.g., via a crafted link), the payload persists and executes when other users view the affected message content.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify Stock Message plugin installationLocate the Stock Message plugin in your application plugin directory or admin panel, and note its installed version numberAffected if The plugin is present and running without recent security patches
-
Compare installed version to any available patched releasesCheck the plugin's version against the vendor's release notes or security advisories for CVE-2025-58267 patch informationAffected if Your version is older than the patched release or no patch is available
-
Inspect stored messages for XSS payloadsQuery the message database table or view all stored messages in the admin interface, looking for script tags, event handlers, or encoded JavaScript in message contentAffected if Any stored messages contain unsanitized script tags or JavaScript event handlers
-
Verify CSRF protection is enabledReview the plugin source code or configuration for anti-CSRF token implementation on message creation/update forms, or test by submitting a request without a tokenAffected if No CSRF token is required or validated when creating/editing messages
-
Check user session logs for crafted link triggersReview access logs or session records for authenticated users accessing message creation endpoints from external sources or suspicious referrersAffected if Requests originated from untrusted sources without proper CSRF validation
You are affected if the Stock Message plugin is installed without CSRF protection and contains stored messages with unescaped HTML/JavaScript content.
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.
From vendor dataImplement anti-CSRF tokens and proper input sanitization/output encoding for all user-supplied content to prevent stored XSS. If a patched version exists, upgrade immediately.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58267 — 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-58267 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