dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-41987

HIGH · 8.6 CVSS v4.0 Published 2024-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
The TEM Opera Plus FM Family Transmitter application interface allows users to perform certain actions via HTTP requests without performing any validity checks to verify the requests. This can be exploited to perform certain actions with administrative privileges if a logged-in user visits a malicious web site.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in TEM Opera Plus FM Family Transmitter web interface. The application fails to validate the origin of HTTP requests, allowing attackers to craft malicious pages that trigger unauthorized administrative actions when a logged-in user visits them.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) for all state-changing operations and validate Origin/Referer headers to ensure requests originate from trusted sources.

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
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm TEM Opera Plus FM web interface is accessible
    Access the transmitter's web interface via its IP address or hostname. If the login page loads, the interface is present.
    Affected if The web interface is reachable and a login page is displayed.
  2. Identify the firmware version
    Log into the web interface and navigate to System Info, Status, or About page. Look for a version number labeled as firmware, software, or system version.
    Affected if The displayed version matches or precedes the version where the CVE was addressed (check vendor advisories for specific version numbers).
  3. Inspect login and administrative forms for anti-CSRF tokens
    View the page source (right-click > View Page Source) of any form that performs state-changing actions (e.g., settings changes, firmware upload, user management). Look for a hidden input field containing a random token value, or check if forms submit to an endpoint that validates a token.
    Affected if Forms lack a hidden CSRF token parameter or the token value appears missing or static across requests.
  4. Verify Origin and Referer header validation
    Use a browser developer tool or a tool like Burp Suite to intercept an HTTP request sent to the transmitter. Check if the server rejects requests with missing or mismatched Origin/Referer headers, or inspect server responses for validation logic.
    Affected if The server accepts requests with arbitrary or missing Origin/Referer headers without rejecting them.
  5. Check cookie security attributes
    In the browser developer tools, go to the Application tab and inspect cookies set by the transmitter. Verify if the session cookie has the SameSite attribute set to Strict or Lax, and if the Secure flag is enabled.
    Affected if The session cookie lacks SameSite attribute or has it set to None without the Secure flag.

A user is affected if the TEM Opera Plus FM web interface is running and administrative forms lack anti-CSRF tokens or do not validate request origins.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (synchronizer token pattern) for all state-changing operations and validate Origin/Referer headers to ensure requests originate from trusted sources.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41987 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41987 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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