dbcve.org
MonitorApplication · Op5

CVE-2012-0261

HIGH · 10.0 CVSS v2.0 Published 2013-12-31
Fix available
A fix is available. Upgrade to after 5.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click

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
license.php in system-portal before 1.6.2 in op5 Monitor and op5 Appliance before 5.5.3 allows remote attackers to execute arbitrary commands via shell metacharacters in the timestamp parameter for an install action.

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

Command injection vulnerability in license.php allows remote attackers to execute arbitrary OS commands by injecting shell metacharacters into the timestamp parameter when performing an install action. The vulnerability affects system-portal before version 1.6.2 in op5 Monitor and op5 Appliance before version 5.5.3.

MitigationUpgrade to system-portal 1.6.2 or op5 Appliance 5.5.3 or later. If immediate patching is not possible, disable the license.php install functionality at the web server level and implement strict input validation on the timestamp parameter to prevent shell metacharacter injection.

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
MonitorApplication
Affected:<= 5.5.1= 5.3.5= 5.4.0= 5.4.2= 5.5.0
System PortalApplication
Affected:<= 1.6.1

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Identify installed op5 product and version
    Check the installed package version or web application version - for op5 Monitor look in /opt/monitor or check RPM packages; for system-portal check the installed version via package manager or web interface
    Affected if Version matches: op5 Monitor <= 5.5.1, 5.3.5, 5.4.0, 5.4.2, 5.5.0 OR system-portal <= 1.6.1 OR op5 Appliance < 5.5.3
  2. Locate license.php file
    Search for license.php in the web document root directory of the op5 Monitor or system-portal installation
    Affected if license.php file exists in the web application directory
  3. Verify install action is accessible
    Check if the install action is enabled in license.php by examining whether the script accepts an 'action=install' parameter or similar install functionality
    Affected if The install action in license.php is accessible and not disabled or removed
  4. Check timestamp parameter handling
    Inspect the license.php code to see how the timestamp parameter is processed - look for unsanitized use in shell commands
    Affected if The timestamp parameter is used in a shell command without proper input validation or escaping of shell metacharacters

If op5 Monitor, system-portal, or op5 Appliance version is within the affected range AND license.php with an install action is accessible, the environment is vulnerable to command injection via the timestamp parameter.

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
Upgrade available Upgrade to a release after 5.5.1
Interim mitigation

Upgrade to system-portal 1.6.2 or op5 Appliance 5.5.3 or later. If immediate patching is not possible, disable the license.php install functionality at the web server level and implement strict input validation on the timestamp parameter to prevent shell metacharacter injection.

Recommended fix High confidence

op5 Monitor 5.5.3+ or op5 System Portal 1.6.2+

  1. Identify whether you are running op5 Monitor or op5 System Portal, and determine the current version
  2. If running op5 Monitor: upgrade to version 5.5.3 or later
  3. If running op5 System Portal: upgrade to version 1.6.2 or later
  4. After upgrade, verify the license.php file has been updated to sanitize the timestamp parameter
  5. Confirm the application is functioning normally post-upgrade

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

Fix this in Monitor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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