dbcve.org
RompagerApplication · Allegrosoft

CVE-2024-0522

HIGH · 8.8 CVSS v3.1 Published 2024-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/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
A vulnerability was found in Allegro RomPager 4.01. It has been classified as problematic. Affected is an unknown function of the file usertable.htm?action=delete of the component HTTP POST Request Handler. The manipulation of the argument username leads to cross-site request forgery. It is possible to launch the attack remotely. Upgrading to version 4.30 is able to address this issue. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-250692. NOTE: The vendor explains that this is a very old issue that got fixed 20 years ago but without a public disclosure.

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 · high confidence

CSRF vulnerability in Allegro RomPager 4.01 allows remote attackers to delete users via crafted HTTP POST requests to usertable.htm?action=delete by manipulating the username argument. The attack requires tricking an authenticated user into submitting a malicious request.

MitigationUpgrade Allegro RomPager to version 4.30 or later to address this CSRF vulnerability. If upgrade is not feasible, implement anti-CSRF tokens in the affected endpoints.

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
RompagerApplication
Affected:= 4.01

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 Allegro RomPager installation and version
    Locate the RomPager installation or check the web server banner/headers. Identify the exact version number of Allegro RomPager software.
    Affected if The installed version is exactly 4.01 (not a later version like 4.30 or above).
  2. Verify web interface accessibility
    Attempt to access the RomPager web management interface via HTTP/HTTPS. Check if the administration console is exposed and reachable.
    Affected if The web interface is accessible and unauthenticated network access to port 80/443 is possible.
  3. Check for usertable.htm endpoint
    Navigate to usertable.htm or attempt a POST request to usertable.htm?action=delete to confirm the endpoint exists and responds.
    Affected if The usertable.htm endpoint exists and responds, indicating user management functionality is enabled.
  4. Confirm user management feature is enabled
    Access the user management section of the RomPager admin interface. Check if user accounts can be viewed, created, or modified.
    Affected if User management features are enabled and accessible to authenticated administrators.

A defender is affected if Allegro RomPager version 4.01 is installed, the web interface is accessible, and the usertable.htm user management endpoint is enabled and reachable.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Allegro RomPager to version 4.30 or later to address this CSRF vulnerability. If upgrade is not feasible, implement anti-CSRF tokens in the affected endpoints.

Recommended fix High confidence

RomPager 4.30

  1. Upgrade the Allegro RomPager installation from version 4.01 to version 4.30 to address the CSRF vulnerability in the usertable.htm delete action handler.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rompager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0522 — 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-0522 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