Skip to content
Noroxi
CVE-2011-1046· NVD / CVE Program· CNA mitre

IBM FileNet P8 Content Engine (aka P8CE) 4.0.1 through 5.0.0, as used in FileNet P8 Content Manager (CM) and FileNet P8 Business Process Man

IBM FileNet P8 Content Engine (aka P8CE) 4.0.1 through 5.0.0, as used in FileNet P8 Content Manager (CM) and FileNet P8 Business Process Manager (BPM), does not require the PRIVILEGED_WRITE access role for all intended Object Store modifications, which allows remote attackers to change a privileged property of an object via unspecified vectors.

MediumCVSS 5.0 · v2.0—No exploit No fix recorded
Published
Feb 21, 2011
Updated
Jun 16, 2026
EPSS
1.2% · 68th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

20

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.2%

Affected systems

VendorProduct
ibmfilenet p8 content engine
ibmfilenet p8 business process manager
ibmfilenet p8 content manager

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • ibm filenet p8 business process managerall versions
  • ibm filenet p8 content engine4.0.1
  • ibm filenet p8 content engine4.0.1.10
  • ibm filenet p8 content engine4.0.1.11
  • ibm filenet p8 content engine4.0.1.12
  • ibm filenet p8 content engine4.0.1.13
  • ibm filenet p8 content engine4.5.0
  • ibm filenet p8 content engine4.5.0.2
  • ibm filenet p8 content engine4.5.1.3
  • ibm filenet p8 content engine4.5.1.4
  • ibm filenet p8 content engine4.5.1.5
  • ibm filenet p8 content engine4.5.1.6
  • ibm filenet p8 content engine5.0.0
  • ibm filenet p8 content managerall versions

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
P · data or configuration can be modified
Availability
none
Attack complexity
Low
Confidentiality impact
None
Integrity impact
P
Availability impact
None

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

All records