CVE-2025-60164
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 NewsMAN NewsmanApp newsmanapp allows Stored XSS.This issue affects NewsmanApp: from n/a through <= 2.7.7.
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 NewsmanApp versions up to 2.7.7 allows attackers to inject malicious scripts through state-changing requests, resulting in Stored XSS. The lack of CSRF protection enables attackers to trick authenticated users into performing unintended actions that persist malicious code in the application.
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 NewsmanApp installationLocate the NewsmanApp application in your environment. Check for the presence of newsman-app directories, web server configurations hosting newsman, or the newsman service running on the system.Affected if NewsmanApp is installed and accessible in the environment.
-
Determine installed versionCheck the version of NewsmanApp currently running. Look for version information in the application admin panel, configuration files, or by querying the application directly (often visible in headers, footer, or /about endpoint).Affected if The installed version is 2.7.7 or any version prior to it.
-
Inspect state-changing endpoints for CSRF tokensExamine the application's state-changing operations (forms, API endpoints that modify data such as user settings, campaign creation, list management). Review the HTML source or API responses to verify if anti-CSRF tokens are included in POST/PUT/DELETE requests.Affected if State-changing requests do not include CSRF tokens or similar protection mechanisms.
-
Test for CSRF vulnerabilityUsing a testing tool or manual request manipulation, send a state-changing request (e.g., modifying user profile, creating a campaign) without the CSRF token to see if the action executes successfully.Affected if The application accepts and processes state-changing requests without validating a CSRF token.
You are affected if NewsmanApp version 2.7.7 or lower is installed and state-changing operations lack CSRF token validation.
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 for all state-changing operations and apply proper input validation with context-aware output encoding to prevent the stored XSS.
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60164 — 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-60164 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